From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: Leonardo Bras <leo.bras@arm.com>, Marc Zyngier <maz@kernel.org>,
Oliver Upton <oupton@kernel.org>,
Fuad Tabba <fuad.tabba@linux.dev>,
Joey Gouly <joey.gouly@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Raghavendra Rao Ananta <rananta@google.com>
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v4 2/3] KVM: arm64: Introduce KVM_PGTABLE_WALK_SKIP_LEVEL* walk flags
Date: Fri, 6 Nov 2026 17:02:31 +0000 [thread overview]
Message-ID: <60fe23f4-4fca-41b6-8489-a28ab7b281f9@arm.com> (raw)
In-Reply-To: <20261106161240.1345126-3-leo.bras@arm.com>
On 06/11/2026 16:12, Leonardo Bras wrote:
> Add new walking flags KVM_PGTABLE_WALK_SKIP_LEVEL{0-3}.
> When used, they make the kvm_pgtable_walk() skip the given level, as well
> as levels higher than that.
>
> Being able to skip levels substancially decreases the runtime of a
minor nit: substantially
> pagetable walk when the callback function does nothing on that level.
>
> Signed-off-by: Leonardo Bras <leo.bras@arm.com>
> ---
> arch/arm64/include/asm/kvm_pgtable.h | 14 ++++++++++++++
> arch/arm64/kvm/hyp/pgtable.c | 16 +++++++++++++---
> 2 files changed, 27 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm64/include/asm/kvm_pgtable.h b/arch/arm64/include/asm/kvm_pgtable.h
> index 41a8687938eb..5f37ceef8d63 100644
> --- a/arch/arm64/include/asm/kvm_pgtable.h
> +++ b/arch/arm64/include/asm/kvm_pgtable.h
> @@ -311,31 +311,45 @@ typedef bool (*kvm_pgtable_force_pte_cb_t)(u64 addr, u64 end,
> * @KVM_PGTABLE_WALK_SHARED: Indicates the page-tables may be shared
> * with other software walkers.
> * @KVM_PGTABLE_WALK_IGNORE_EAGAIN: Don't terminate the walk early if
> * the walker returns -EAGAIN.
> * @KVM_PGTABLE_WALK_SKIP_BBM_TLBI: Visit and update table entries
> * without Break-before-make's
> * TLB invalidation.
> * @KVM_PGTABLE_WALK_SKIP_CMO: Visit and update table entries
> * without Cache maintenance
> * operations required.
> + * @KVM_PGTABLE_WALK_SKIP_LEVEL0: Skip visiting level 0+ entries
> + * @KVM_PGTABLE_WALK_SKIP_LEVEL1: Skip visiting level 1+ entries
> + * @KVM_PGTABLE_WALK_SKIP_LEVEL2: Skip visiting level 2+ entries
> + * @KVM_PGTABLE_WALK_SKIP_LEVEL3: Skip visiting level 3 entries
> */
> enum kvm_pgtable_walk_flags {
> KVM_PGTABLE_WALK_LEAF = BIT(0),
> KVM_PGTABLE_WALK_TABLE_PRE = BIT(1),
> KVM_PGTABLE_WALK_TABLE_POST = BIT(2),
> KVM_PGTABLE_WALK_SHARED = BIT(3),
> KVM_PGTABLE_WALK_IGNORE_EAGAIN = BIT(4),
> KVM_PGTABLE_WALK_SKIP_BBM_TLBI = BIT(5),
> KVM_PGTABLE_WALK_SKIP_CMO = BIT(6),
> + /* SKIP_LEVEL* flags should not be split nor reordered */
> + KVM_PGTABLE_WALK_SKIP_LEVEL0 = BIT(7),
> + KVM_PGTABLE_WALK_SKIP_LEVEL1 = BIT(8),
> + KVM_PGTABLE_WALK_SKIP_LEVEL2 = BIT(9),
> + KVM_PGTABLE_WALK_SKIP_LEVEL3 = BIT(10),
> };
>
> +#define KVM_PGTABLE_WALK_SKIP_LEVELS (KVM_PGTABLE_WALK_SKIP_LEVEL0 | \
> + KVM_PGTABLE_WALK_SKIP_LEVEL1 | \
> + KVM_PGTABLE_WALK_SKIP_LEVEL2 | \
> + KVM_PGTABLE_WALK_SKIP_LEVEL3 )
> +
> struct kvm_pgtable_visit_ctx {
> kvm_pte_t *ptep;
> kvm_pte_t old;
> void *arg;
> struct kvm_pgtable_mm_ops *mm_ops;
> u64 start;
> u64 addr;
> u64 end;
> s8 level;
> enum kvm_pgtable_walk_flags flags;
> diff --git a/arch/arm64/kvm/hyp/pgtable.c b/arch/arm64/kvm/hyp/pgtable.c
> index 7a51f78b6446..80744478c810 100644
> --- a/arch/arm64/kvm/hyp/pgtable.c
> +++ b/arch/arm64/kvm/hyp/pgtable.c
> @@ -137,20 +137,27 @@ static bool kvm_pgtable_walk_continue(const struct kvm_pgtable_walker *walker,
> * Ignore the return code altogether for walkers outside a fault handler
> * (e.g. write protecting a range of memory) and chug along with the
> * page table walk.
> */
> if (r == -EAGAIN)
> return walker->flags & KVM_PGTABLE_WALK_IGNORE_EAGAIN;
>
> return !r;
> }
>
> +static bool kvm_pgtable_skip_level(s8 level, enum kvm_pgtable_walk_flags flags)
> +{
> + u32 skip = FIELD_GET(KVM_PGTABLE_WALK_SKIP_LEVELS, flags);
> +
> + return unlikely(skip && level >= ffs(skip) - 1);
> +}
> +
> static int __kvm_pgtable_walk(struct kvm_pgtable_walk_data *data,
> struct kvm_pgtable_mm_ops *mm_ops, kvm_pteref_t pgtable, s8 level);
>
> static inline int __kvm_pgtable_visit(struct kvm_pgtable_walk_data *data,
> struct kvm_pgtable_mm_ops *mm_ops,
> kvm_pteref_t pteref, s8 level)
> {
> enum kvm_pgtable_walk_flags flags = data->walker->flags;
> kvm_pte_t *ptep = kvm_dereference_pteref(data->walker, pteref);
> struct kvm_pgtable_visit_ctx ctx = {
> @@ -185,35 +192,35 @@ static inline int __kvm_pgtable_visit(struct kvm_pgtable_walk_data *data,
> * into a newly installed or replaced table.
> */
> if (reload) {
> ctx.old = READ_ONCE(*ptep);
> table = kvm_pte_table(ctx.old, level);
> }
>
> if (!kvm_pgtable_walk_continue(data->walker, ret))
> return ret;
>
> - if (!table) {
> + if (!table || kvm_pgtable_skip_level(level + 1, ctx.flags)) {
> data->addr = ALIGN_DOWN(data->addr, kvm_granule_size(level));
> data->addr += kvm_granule_size(level);
> goto out;
> }
>
> childp = (kvm_pteref_t)kvm_pte_follow(ctx.old, mm_ops);
> ret = __kvm_pgtable_walk(data, mm_ops, childp, level + 1);
> if (!kvm_pgtable_walk_continue(data->walker, ret))
> return ret;
>
> - if (ctx.flags & KVM_PGTABLE_WALK_TABLE_POST)
> +out:
> + if (table && ctx.flags & KVM_PGTABLE_WALK_TABLE_POST)
> ret = kvm_pgtable_visitor_cb(data, &ctx, KVM_PGTABLE_WALK_TABLE_POST);
>
> -out:
> if (kvm_pgtable_walk_continue(data->walker, ret))
> return 0;
>
> return ret;
> }
>
> static int __kvm_pgtable_walk(struct kvm_pgtable_walk_data *data,
> struct kvm_pgtable_mm_ops *mm_ops, kvm_pteref_t pgtable, s8 level)
> {
> u32 idx;
> @@ -242,20 +249,23 @@ static int _kvm_pgtable_walk(struct kvm_pgtable *pgt, struct kvm_pgtable_walk_da
> u32 idx;
> int ret = 0;
> u64 limit = BIT(pgt->ia_bits);
>
> if (data->addr > limit || data->end > limit)
> return -ERANGE;
>
> if (!pgt->pgd)
> return -EINVAL;
>
> + if (kvm_pgtable_skip_level(pgt->start_level, data->walker->flags))
> + return 0;
> +
Should we rather return an error here ? A walk skipping the start level,
is that any meaningful ?
Suzuki
> for (idx = kvm_pgd_page_idx(pgt, data->addr); data->addr < data->end; ++idx) {
> kvm_pteref_t pteref = &pgt->pgd[idx * PTRS_PER_PTE];
>
> ret = __kvm_pgtable_walk(data, pgt->mm_ops, pteref, pgt->start_level);
> if (ret)
> break;
> }
>
> return ret;
> }
next prev parent reply other threads:[~2026-11-06 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 16:12 [PATCH RESEND v4 0/3] Optimize S2 hugepage splitting, introduce skip-level flags Leonardo Bras
2026-11-06 16:12 ` [PATCH RESEND v4 1/3] KVM: arm64: Avoid re-testing walk_continue Leonardo Bras
2026-11-06 16:59 ` Suzuki K Poulose
2026-11-06 16:12 ` [PATCH RESEND v4 2/3] KVM: arm64: Introduce KVM_PGTABLE_WALK_SKIP_LEVEL* walk flags Leonardo Bras
2026-11-06 17:02 ` Suzuki K Poulose [this message]
2026-11-06 18:13 ` Oliver Upton
2026-11-06 16:12 ` [PATCH RESEND v4 3/3] KVM: arm64: Make stage2_split_walker() skip unnecessary walks Leonardo Bras
2026-11-06 16:57 ` [PATCH RESEND v4 0/3] Optimize S2 hugepage splitting, introduce skip-level flags Marc Zyngier
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=60fe23f4-4fca-41b6-8489-a28ab7b281f9@arm.com \
--to=suzuki.poulose@arm.com \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=leo.bras@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=oupton@kernel.org \
--cc=rananta@google.com \
--cc=seiden@linux.ibm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.com \
/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
all inboxes | Powered by JetHome®