From: sashiko-bot@kernel.org
To: "Gautam Menghani" <gautam@linux.ibm.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v3] KVM: PPC: Book3S HV: Avoid spurious interrupts caused by LPCR_MER bit
Date: Mon, 21 Sep 2026 11:25:38 +0000 [thread overview]
Message-ID: <20260921112538.ED7101F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260921111043.49825-1-gautam@linux.ibm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] kvm: ppc: lost LPCR_MER interrupts for XICS due to XIVE state leak
--
commit 215dda3f95780a965ce67c9c452b6f7d1948e486
Author: Gautam Menghani <gautam@linux.ibm.com>
KVM: PPC: Book3S HV: Avoid spurious interrupts caused by LPCR_MER bit
This commit avoids spurious interrupts for KVM on PowerNV guests by not
setting the LPCR_MER bit when native XIVE is available. It introduces a new
helper, kvmppc_xive_native_enabled(), to check for native XIVE and skips
setting LPCR_MER if it evaluates to true.
Closes: https://lore.kernel.org/linuxppc-dev/582904882.11159.1786719390349.JavaMail.zimbra@raptorengineeringinc.com
> diff --git a/arch/powerpc/include/asm/kvm_ppc.h b/arch/powerpc/include/asm/kvm_ppc.h
> index 169ea6a7fbad4..580ad2548c2bf 100644
> --- a/arch/powerpc/include/asm/kvm_ppc.h
> +++ b/arch/powerpc/include/asm/kvm_ppc.h
> @@ -747,6 +747,11 @@ static inline int kvmppc_xive_enabled(struct kvm_vcpu *vcpu)
> return vcpu->arch.irq_type == KVMPPC_IRQ_XIVE;
> }
>
> +static inline bool kvmppc_xive_native_enabled(struct kvm *kvm)
> +{
> + return kvm->arch.xive_devices.native;
> +}
> +
[ ... ]
> diff --git a/arch/powerpc/kvm/book3s_hv.c b/arch/powerpc/kvm/book3s_hv.c
> index dbac3573b2c89..cb2bb29451a7f 100644
> --- a/arch/powerpc/kvm/book3s_hv.c
> +++ b/arch/powerpc/kvm/book3s_hv.c
> @@ -4980,7 +4980,7 @@ int kvmhv_run_single_vcpu(struct kvm_vcpu *vcpu, u64 time_limit,
> if (!kvmhv_on_pseries() && (__kvmppc_get_msr_hv(vcpu) & MSR_EE))
> kvmppc_inject_interrupt_hv(vcpu,
> BOOK3S_INTERRUPT_EXTERNAL, 0);
> - else
> + else if (!kvmppc_xive_native_enabled(vcpu->kvm))
> lpcr |= LPCR_MER;
> } else {
> /*
[Severity: High]
Does kvmppc_xive_native_enabled() accurately reflect whether XIVE is currently
in use?
If a VM switches from XIVE to XICS (such as during a kexec or CAS
renegotiation), the XIVE native device is destroyed. However, the native
pointer is intentionally not cleared:
arch/powerpc/kvm/book3s_xive_native.c:kvmppc_xive_native_release() {
...
/*
* A reference of the kvmppc_xive pointer is now kept under
* the xive_devices struct of the machine for reuse. It is
* freed when the VM is destroyed for now until we fix all the
* execution paths.
*/
kfree(dev);
}
When running in XICS mode after this switch, kvmppc_xive_native_enabled()
will continue to evaluate to true.
Will this cause KVM to bypass setting LPCR_MER, and subsequently fail to
inject external interrupts when MSR_EE=0, resulting in a guest hang?
Could this check instead evaluate the active vCPU IRQ routing, for example by
using !kvmppc_xive_enabled(vcpu)?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260921111043.49825-1-gautam@linux.ibm.com?part=1
next prev parent reply other threads:[~2026-09-21 11:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 11:10 [PATCH v3] KVM: PPC: Book3S HV: Avoid spurious interrupts caused by LPCR_MER bit Gautam Menghani
2026-09-21 11:25 ` sashiko-bot [this message]
2026-09-22 5:59 ` Gautam Menghani
2026-09-23 3:38 ` Narayana Murty N
2026-10-01 3:58 ` Gautam Menghani
2026-09-23 7:01 ` Mukesh Kumar Chaurasiya
2026-09-23 12:50 ` Gautam Menghani
2026-10-05 8:00 ` Amit Machhiwal
2026-10-05 8:31 ` Gautam Menghani
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=20260921112538.ED7101F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=gautam@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 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.