From: sashiko-bot@kernel.org
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v7 7/8] KVM: selftests: Only warn for idle-page checks on powerpc pseries LPAR
Date: Tue, 06 Oct 2026 16:16:03 +0000 [thread overview]
Message-ID: <sashiko-outbox-162228@kernel.org> (raw)
In-Reply-To: <0227000da4e6fe69b278dc971b74b3f65b73ead9.1791280439.git.ritesh.list@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] selftests: typo 'explicitely' in comment
--
commit 87fed9598d0ceb8998ad38373e71f38a0d2446ab
Author: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
KVM: selftests: Only warn for idle-page checks on powerpc pseries LPAR
This commit updates the access tracking selftest for KVM to only warn on
idle-page checks when running nested on powerpc pseries LPAR. It uses a new
kvm_is_ppc_pseries_lpar() check to detect this condition because nested KVM
on powerpc does not explicitly flush the TLB for access bit updates.
[ ... ]
> diff --git a/tools/testing/selftests/kvm/access_tracking_perf_test.c b/tools/testing/selftests/kvm/access_tracking_perf_test.c
> index 4415c94b28660..eb6939065e793 100644
> --- a/tools/testing/selftests/kvm/access_tracking_perf_test.c
> +++ b/tools/testing/selftests/kvm/access_tracking_perf_test.c
> @@ -471,6 +471,16 @@ static int access_tracking_unreliable(void)
> return 1;
> }
> #endif
> + /*
> + * PowerPC: Nested KVM (pSeries LPAR) can hide accessed/idle, since KVM
> + * doesn't explicitely flush the TLB for access bit update. L0 keeps
[Severity: Low]
This isn't a bug, but there appears to be a typo here. Should explicitely be
spelled explicitly?
> + * translations cached so the guest won't see the idle bit cleared.
> + */
> + if (kvm_is_ppc_pseries_lpar()) {
> + puts("Skipping idle page count sanity check, because the test is run nested");
> + return 1;
> + }
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1791280439.git.ritesh.list@gmail.com?part=7
next prev parent reply other threads:[~2026-10-06 16:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 10:28 [PATCH v7 0/8] KVM: selftests: add powerpc support Ritesh Harjani (IBM)
2026-10-06 10:28 ` [PATCH v7 1/8] KVM: selftests: Don't limit LE dirty-bitmap bitops to s390x Ritesh Harjani (IBM)
2026-10-06 10:28 ` [PATCH v7 2/8] KVM: selftests: Move memslot_perf_test off the 256M ELF load address Ritesh Harjani (IBM)
2026-10-06 10:28 ` [PATCH v7 3/8] KVM: selftests: Skip the max vCPU ID test when KVM_CAP_PPC_SMT is set Ritesh Harjani (IBM)
2026-10-06 10:28 ` [PATCH v7 4/8] KVM: PPC: selftests: add support for powerpc Ritesh Harjani (IBM)
2026-10-06 10:28 ` [PATCH v7 5/8] KVM: selftests: Add helper for checking if running on powerpc pseries LPAR Ritesh Harjani (IBM)
2026-10-06 10:28 ` [PATCH v7 6/8] KVM: selftests: Skip kvm_create_max_vcpus " Ritesh Harjani (IBM)
2026-10-06 10:28 ` [PATCH v7 7/8] KVM: selftests: Only warn for idle-page checks " Ritesh Harjani (IBM)
2026-10-06 16:16 ` sashiko-bot [this message]
2026-10-06 10:28 ` [PATCH v7 8/8] KVM: selftests: Skip hardware_disable_test " Ritesh Harjani (IBM)
2026-10-07 17:18 ` [PATCH v7 0/8] KVM: selftests: add powerpc support Gautam Menghani
2026-10-12 3:51 ` Madhavan Srinivasan
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=sashiko-outbox-162228@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
/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.