From: Anshuman Khandual <anshuman.khandual@arm.com>
To: arm-kernel@lists.infradead.org
Cc: Marc Zyngier <maz@kernel.org>,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Ard Biesheuvel <ardb@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/8] arm64/mm: Drop PXD_TABLE_BIT
Date: Fri, 28 Feb 2025 09:12:38 +0530 [thread overview]
Message-ID: <ccbe751d-9022-4c66-b894-73b3788f7050@arm.com> (raw)
In-Reply-To: <20250221044227.1145393-1-anshuman.khandual@arm.com>
On 2/21/25 10:12, Anshuman Khandual wrote:
> Remove the PXX_TABLE_BIT definitions and instead rely on PXX_TYPE_MASK,
> PXX_TYPE_SECT and PXX_TYPE_TABLE. The latter versions are more abstract
> and also include the PTE_VALID bit.
>
> This abstraction is valuable for the impending D128 page table support,
> which doesn't have a single page table bit to determine table vs block.
> Instead it has the skip level (SKL) field, where it will consider 0 to
> mean table and any other value to mean a block entry. So PXX_TABLE_BIT
> therefore doesn't fit into the D128 model well, but the type fields do.
>
> This series applies on v6.14-rc3.
>
> Changes in V2:
>
> - Changed pmd_mkhuge() and pud_mkhuge() implementation
> - Changed pud_bad() implementation with an additional patch
>
> Changes in V1:
>
> https://lore.kernel.org/all/20241005123824.1366397-1-anshuman.khandual@arm.com/
>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Oliver Upton <oliver.upton@linux.dev>
> Cc: James Morse <james.morse@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> Cc: kvmarm@lists.linux.dev
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
>
> Anshuman Khandual (6):
> KVM: arm64: ptdump: Test PMD_TYPE_MASK for block mapping
> arm64/ptdump: Test PMD_TYPE_MASK for block mapping
> arm64/mm: Clear PXX_TYPE_MASK in mk_[pmd|pud]_sect_prot()
> arm64/mm: Clear PXX_TYPE_MASK and set PXD_TYPE_SECT in [pmd|pud]_mkhuge()
> arm64/mm: Check PXD_TYPE_TABLE in [p4d|pgd]_bad()
> arm64/mm: Drop PXD_TABLE_BIT
>
> Ryan Roberts (2):
> arm64/mm: Check PUD_TYPE_TABLE in pud_bad()
> arm64/mm: Check pmd_table() in pmd_trans_huge()
>
> arch/arm64/include/asm/pgtable-hwdef.h | 5 --
> arch/arm64/include/asm/pgtable.h | 65 ++++++++++++++++++--------
> arch/arm64/kvm/ptdump.c | 4 +-
> arch/arm64/mm/ptdump.c | 4 +-
> 4 files changed, 50 insertions(+), 28 deletions(-)
>
Gentle ping, just wondering any updates on the series.
next prev parent reply other threads:[~2025-02-28 4:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 4:42 [PATCH V2 0/8] arm64/mm: Drop PXD_TABLE_BIT Anshuman Khandual
2025-02-21 4:42 ` [PATCH V2 1/8] KVM: arm64: ptdump: Test PMD_TYPE_MASK for block mapping Anshuman Khandual
2025-03-11 18:10 ` Catalin Marinas
2025-03-11 18:22 ` Marc Zyngier
2025-02-21 4:42 ` [PATCH V2 2/8] arm64/ptdump: " Anshuman Khandual
2025-02-21 4:42 ` [PATCH V2 3/8] arm64/mm: Clear PXX_TYPE_MASK in mk_[pmd|pud]_sect_prot() Anshuman Khandual
2025-02-21 4:42 ` [PATCH V2 4/8] arm64/mm: Clear PXX_TYPE_MASK and set PXD_TYPE_SECT in [pmd|pud]_mkhuge() Anshuman Khandual
2025-02-21 4:42 ` [PATCH V2 5/8] arm64/mm: Check PXD_TYPE_TABLE in [p4d|pgd]_bad() Anshuman Khandual
2025-02-21 4:42 ` [PATCH V2 6/8] arm64/mm: Check PUD_TYPE_TABLE in pud_bad() Anshuman Khandual
2025-02-21 4:42 ` [PATCH V2 7/8] arm64/mm: Check pmd_table() in pmd_trans_huge() Anshuman Khandual
2025-02-21 4:42 ` [PATCH V2 8/8] arm64/mm: Drop PXD_TABLE_BIT Anshuman Khandual
2025-02-28 3:42 ` Anshuman Khandual [this message]
2025-02-28 15:32 ` [PATCH V2 0/8] " Ryan Roberts
2025-03-03 5:02 ` Anshuman Khandual
2025-03-03 10:23 ` Ryan Roberts
2025-03-10 6:38 ` Anshuman Khandual
2025-03-12 18:09 ` Catalin Marinas
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=ccbe751d-9022-4c66-b894-73b3788f7050@arm.com \
--to=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=arm-kernel@lists.infradead.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=ryan.roberts@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 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).