From: sashiko-bot@kernel.org
To: "Amit Machhiwal" <amachhiw@linux.ibm.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v9 2/4] KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM
Date: Sat, 08 Aug 2026 16:39:02 +0000 [thread overview]
Message-ID: <20260808163902.E1F4F1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260808161148.66673-3-amachhiw@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] KVM_CAP_PPC_COMPAT_CAPS advertises capability support on all pseries hosts, but the KVM_PPC_GET_COMPAT_CAPS ioctl fails with -EINVAL on non-nestedv2 pseries hosts.
--
--- Patch [2]: [PATCH v9 2/4] KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM ---
commit 48012da6c0966da1bf70f356cb9a87c22af64308
Author: Amit Machhiwal <amachhiw@linux.ibm.com>
KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM
This commit adds support for retrieving host CPU compatibility capabilities
for nested guests on PowerVM via a new ioctl, KVM_PPC_GET_COMPAT_CAPS. It
retrieves the cached capabilities negotiated via the H_GUEST_GET_CAPABILITIES
hcall for nestedv2 systems.
> diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
> index 61dbeea317f3b..8799124b80960 100644
> --- a/arch/powerpc/kvm/book3s_hv.c
> +++ b/arch/powerpc/kvm/book3s_hv.c
[ ... ]
> @@ -6510,6 +6510,25 @@ static bool kvmppc_hash_v3_possible(void)
> return true;
> }
>
> +
> +static int kvmppc_get_compat_caps(struct kvm_ppc_compat_caps *host_caps)
> +{
> + unsigned long capabilities = 0;
> + long rc = -EINVAL;
> +
> + if (kvmhv_on_pseries()) {
> + if (kvmhv_is_nestedv2()) {
> + WARN_ON_ONCE(!nested_capabilities);
> + capabilities = nested_capabilities;
> + rc = 0;
> + }
> + }
> +
[Severity: High]
KVM_CAP_PPC_COMPAT_CAPS appears to be advertised for all pseries hosts in
kvm_vm_ioctl_check_extension():
case KVM_CAP_PPC_COMPAT_CAPS:
r = 0;
if (hv_enabled && kvmhv_on_pseries())
r = 1;
break;
But here in kvmppc_get_compat_caps(), the ioctl returns -EINVAL for
non-nestedv2 pseries hosts.
Will this mismatch cause userspace (like QEMU) to fail during guest
initialization if it sees the capability is supported on a non-nestedv2
host, but the ioctl unexpectedly fails with -EINVAL?
> + host_caps->compat_capabilities = capabilities & KVM_PPC_COMPAT_BITMASK;
> +
> + return rc;
> +}
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260808161148.66673-1-amachhiw@linux.ibm.com?part=2
next prev parent reply other threads:[~2026-08-08 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 16:11 [PATCH v9 0/4] KVM: PPC: Expose CPU compatibility modes for nested guests Amit Machhiwal
2026-08-08 16:11 ` [PATCH v9 1/4] KVM: PPC: Introduce KVM_CAP_PPC_COMPAT_CAPS and wire up ioctl Amit Machhiwal
2026-08-08 16:23 ` sashiko-bot
2026-08-08 16:11 ` [PATCH v9 2/4] KVM: PPC: Book3S HV: Implement compat CPU capability retrieval for KVM on PowerVM Amit Machhiwal
2026-08-08 16:39 ` sashiko-bot [this message]
2026-08-08 16:11 ` [PATCH v9 3/4] KVM: PPC: Book3S HV: Add support for compat CPU capabilities for KVM on PowerNV Amit Machhiwal
2026-08-08 16:11 ` [PATCH v9 4/4] KVM: PPC: Document KVM_PPC_GET_COMPAT_CAPS ioctl Amit Machhiwal
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=20260808163902.E1F4F1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=amachhiw@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox