From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [BUG] LPAE can be enabled with non-LPAE capable CPUs
Date: Tue, 14 Feb 2012 12:20:10 +0000 [thread overview]
Message-ID: <20120214122010.GC13673@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20120214121544.GB9050@arm.com>
On Tue, Feb 14, 2012 at 12:15:44PM +0000, Catalin Marinas wrote:
> It makes sense. Something like this, unless you've already done it (I
> also changed to CPU_32v7 for consistency):
Looks good, please put it in the patch system, thanks.
> commit d8d34065edfdc1b81f6e3886e15b5c2b2bd30b4e
> Author: Catalin Marinas <catalin.marinas@arm.com>
> Date: Tue Feb 14 12:12:58 2012 +0000
>
> ARM: Do not allow ARM_LPAE on pre-ARMv7 architectures
>
> This patch expands the Kconfig dependencies for ARM_LPAE to not allow
> enabling when architectures other than ARMv7 are built into the kernel.
>
> Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
> Reported-by: Russell King <linux@arm.linux.org.uk>
>
> diff --git a/arch/arm/mm/Kconfig b/arch/arm/mm/Kconfig
> index 1a3ca24..7edef91 100644
> --- a/arch/arm/mm/Kconfig
> +++ b/arch/arm/mm/Kconfig
> @@ -631,7 +631,8 @@ comment "Processor Features"
>
> config ARM_LPAE
> bool "Support for the Large Physical Address Extension"
> - depends on MMU && CPU_V7
> + depends on MMU && CPU_32v7 && !CPU_32v6 && !CPU_32v5 && \
> + !CPU_32v4 && !CPU_32v3
> help
> Say Y if you have an ARMv7 processor supporting the LPAE page
> table format and you would like to access memory beyond the
>
>
> --
> Catalin
prev parent reply other threads:[~2012-02-14 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 8:21 [BUG] LPAE can be enabled with non-LPAE capable CPUs Russell King - ARM Linux
2012-02-14 12:15 ` Catalin Marinas
2012-02-14 12:20 ` Russell King - ARM Linux [this message]
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=20120214122010.GC13673@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).