From: James Hogan <james.hogan@imgtec.com>
To: Paul Burton <paul.burton@imgtec.com>
Cc: <linux-mips@linux-mips.org>, Ralf Baechle <ralf@linux-mips.org>,
"Paul Gortmaker" <paul.gortmaker@windriver.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 13/13] MIPS: mm: Panic if an XPA kernel is run without RIXI
Date: Mon, 18 Apr 2016 11:04:47 +0100 [thread overview]
Message-ID: <20160418100446.GN7859@jhogan-linux.le.imgtec.org> (raw)
In-Reply-To: <1460972133-16973-14-git-send-email-paul.burton@imgtec.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Mon, Apr 18, 2016 at 10:35:33AM +0100, Paul Burton wrote:
> XPA kernels hardcode for the presence of RIXI - the PTE format & its
> handling presume RI & XI bits. Make this dependence explicit by panicing
> if we run on a system that violates it.
>
> Signed-off-by: Paul Burton <paul.burton@imgtec.com>
>
> ---
>
> Changes in v2:
> - New patch, in response to clarification on patch 5.
>
> arch/mips/mm/tlbex.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/mips/mm/tlbex.c b/arch/mips/mm/tlbex.c
> index 3f1a8a2..9c39c66 100644
> --- a/arch/mips/mm/tlbex.c
> +++ b/arch/mips/mm/tlbex.c
> @@ -2395,6 +2395,9 @@ void build_tlb_refill_handler(void)
> */
> static int run_once = 0;
>
> + if (config_enabled(CONFIG_XPA) && !cpu_has_rixi)
> + panic("Kernels supporting XPA currently require CPUs with RIXI\n");
Don't think you need the newline.
Otherwise
Reviewed-by: James Hogan <james.hogan@imgtec.com>
In the future we can hopefully drop that requirement so that XPA kernels
can run on non-XPA, non-RIXI hardware.
Cheers
James
> +
> output_pgtable_bits_defines();
> check_pabits();
>
> --
> 2.8.0
>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-18 10:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1460972133-16973-1-git-send-email-paul.burton@imgtec.com>
2016-04-18 9:35 ` [PATCH v2 01/13] MIPS: Separate XPA CPU feature into LPA and MVH Paul Burton
2016-04-18 9:35 ` [PATCH v2 02/13] MIPS: Fix HTW config on XPA kernel without LPA enabled Paul Burton
2016-04-18 9:35 ` [PATCH v2 03/13] MIPS: Remove redundant asm/pgtable-bits.h inclusions Paul Burton
2016-04-18 12:36 ` Sergei Shtylyov
2016-04-18 9:35 ` [PATCH v2 04/13] MIPS: Use enums to make asm/pgtable-bits.h readable Paul Burton
2016-04-18 9:35 ` [PATCH v2 06/13] MIPS: mm: Unify pte_page definition Paul Burton
2016-04-18 9:35 ` [PATCH v2 08/13] MIPS: mm: Don't clobber $1 on XPA TLB refill Paul Burton
2016-04-18 9:35 ` [PATCH v2 09/13] MIPS: mm: Pass scratch register through to iPTE_SW Paul Burton
2016-04-18 9:35 ` [PATCH v2 10/13] MIPS: mm: Be more explicit about PTE mode bit handling Paul Burton
2016-04-18 9:35 ` [PATCH v2 11/13] MIPS: mm: Simplify build_update_entries Paul Burton
2016-04-18 9:35 ` [PATCH v2 12/13] MIPS: mm: Don't do MTHC0 if XPA not present Paul Burton
2016-04-18 9:35 ` [PATCH v2 13/13] MIPS: mm: Panic if an XPA kernel is run without RIXI Paul Burton
2016-04-18 10:04 ` James Hogan [this message]
[not found] ` <1460972133-16973-8-git-send-email-paul.burton@imgtec.com>
2016-04-18 14:34 ` [PATCH v2 07/13] MIPS: mm: Fix MIPS32 36b physical addressing (alchemy, netlogic) Manuel Lauss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160418100446.GN7859@jhogan-linux.le.imgtec.org \
--to=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=paul.burton@imgtec.com \
--cc=paul.gortmaker@windriver.com \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome