From: Catalin Marinas <catalin.marinas@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, suzuki.poulose@arm.com,
mark.rutland@arm.com, will@kernel.org, maz@kernel.org,
james.morse@arm.com, steven.price@arm.com
Subject: Re: [RFC V2 10/10] arm64/mm: Enable CONFIG_ARM64_PA_BITS_52 on CONFIG_ARM64_[4K|16K]_PAGES
Date: Thu, 5 Aug 2021 18:23:15 +0100 [thread overview]
Message-ID: <20210805172314.GF6719@arm.com> (raw)
In-Reply-To: <1627281445-12445-11-git-send-email-anshuman.khandual@arm.com>
On Mon, Jul 26, 2021 at 12:07:25PM +0530, Anshuman Khandual wrote:
> All required FEAT_LPA2 components for 52 bit PA range are already in place.
> Just enable CONFIG_ARM64_PA_BITS_52 on 4K and 16K pages which would select
> CONFIG_ARM64_PA_BITS_52_LPA2 activating 52 bit PA range via FEAT_LPA2.
>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> arch/arm64/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 1999ac6..ce139415 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -952,9 +952,9 @@ config ARM64_PA_BITS_48
>
> config ARM64_PA_BITS_52
> bool "52-bit (ARMv8.2)"
> - depends on ARM64_64K_PAGES
> depends on ARM64_PAN || !ARM64_SW_TTBR0_PAN
> select ARM64_PA_BITS_52_LPA if ARM64_64K_PAGES
> + select ARM64_PA_BITS_52_LPA2 if (ARM64_4K_PAGES || ARM64_16K_PAGES)
> help
> Enable support for a 52-bit physical address space, introduced as
> part of the ARMv8.2-LPA extension.
If you do it this way, the text here needs updating and the 8.2
architecture version removed.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, suzuki.poulose@arm.com,
mark.rutland@arm.com, will@kernel.org, maz@kernel.org,
james.morse@arm.com, steven.price@arm.com
Subject: Re: [RFC V2 10/10] arm64/mm: Enable CONFIG_ARM64_PA_BITS_52 on CONFIG_ARM64_[4K|16K]_PAGES
Date: Thu, 5 Aug 2021 18:23:15 +0100 [thread overview]
Message-ID: <20210805172314.GF6719@arm.com> (raw)
In-Reply-To: <1627281445-12445-11-git-send-email-anshuman.khandual@arm.com>
On Mon, Jul 26, 2021 at 12:07:25PM +0530, Anshuman Khandual wrote:
> All required FEAT_LPA2 components for 52 bit PA range are already in place.
> Just enable CONFIG_ARM64_PA_BITS_52 on 4K and 16K pages which would select
> CONFIG_ARM64_PA_BITS_52_LPA2 activating 52 bit PA range via FEAT_LPA2.
>
> Signed-off-by: Anshuman Khandual <anshuman.khandual@arm.com>
> ---
> arch/arm64/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 1999ac6..ce139415 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -952,9 +952,9 @@ config ARM64_PA_BITS_48
>
> config ARM64_PA_BITS_52
> bool "52-bit (ARMv8.2)"
> - depends on ARM64_64K_PAGES
> depends on ARM64_PAN || !ARM64_SW_TTBR0_PAN
> select ARM64_PA_BITS_52_LPA if ARM64_64K_PAGES
> + select ARM64_PA_BITS_52_LPA2 if (ARM64_4K_PAGES || ARM64_16K_PAGES)
> help
> Enable support for a 52-bit physical address space, introduced as
> part of the ARMv8.2-LPA extension.
If you do it this way, the text here needs updating and the 8.2
architecture version removed.
--
Catalin
next prev parent reply other threads:[~2021-08-05 17:25 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 6:37 [RFC V2 00/10] arm64/mm: Enable FEAT_LPA2 (52 bits PA support on 4K|16K pages) Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-07-26 6:37 ` [RFC V2 01/10] mm/mmap: Dynamically initialize protection_map[] Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-08-05 17:03 ` Catalin Marinas
2021-08-05 17:03 ` Catalin Marinas
2021-08-12 9:15 ` Anshuman Khandual
2021-08-12 9:15 ` Anshuman Khandual
2021-08-13 7:16 ` Anshuman Khandual
2021-08-13 7:16 ` Anshuman Khandual
2021-07-26 6:37 ` [RFC V2 02/10] arm64/mm: Consolidate TCR_EL1 fields Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-08-05 17:05 ` Catalin Marinas
2021-08-05 17:05 ` Catalin Marinas
2021-07-26 6:37 ` [RFC V2 03/10] arm64/mm: Add FEAT_LPA2 specific TCR_EL1.DS field Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-08-05 17:06 ` Catalin Marinas
2021-08-05 17:06 ` Catalin Marinas
2021-07-26 6:37 ` [RFC V2 04/10] arm64/mm: Add FEAT_LPA2 specific ID_AA64MMFR0.TGRAN[2] Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-08-05 17:06 ` Catalin Marinas
2021-08-05 17:06 ` Catalin Marinas
2021-07-26 6:37 ` [RFC V2 05/10] arm64/mm: Add CONFIG_ARM64_PA_BITS_52_[LPA|LPA2] Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-08-05 17:25 ` Catalin Marinas
2021-08-05 17:25 ` Catalin Marinas
2021-08-12 10:09 ` Anshuman Khandual
2021-08-12 10:09 ` Anshuman Khandual
2021-07-26 6:37 ` [RFC V2 06/10] arm64/mm: Add FEAT_LPA2 specific encoding Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-07-26 6:37 ` [RFC V2 07/10] arm64/mm: Detect and enable FEAT_LPA2 Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-07-26 6:37 ` [RFC V2 08/10] arm64/mm: Add FEAT_LPA2 specific PTE_SHARED and PMD_SECT_S Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-07-26 6:37 ` [RFC V2 09/10] arm64/mm: Add FEAT_LPA2 specific fallback (48 bits PA) when not implemented Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-07-26 6:37 ` [RFC V2 10/10] arm64/mm: Enable CONFIG_ARM64_PA_BITS_52 on CONFIG_ARM64_[4K|16K]_PAGES Anshuman Khandual
2021-07-26 6:37 ` Anshuman Khandual
2021-08-05 17:23 ` Catalin Marinas [this message]
2021-08-05 17:23 ` Catalin Marinas
2021-08-12 9:13 ` Anshuman Khandual
2021-08-12 9:13 ` Anshuman Khandual
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=20210805172314.GF6719@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.