From: "Markku Ahvenjärvi" <mankku@gmail.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Cc: mankku@gmail.com, janne.karhunen@gmail.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/1] KVM: nVMX: update VPPR on vmlaunch/vmresume
Date: Fri, 20 Sep 2024 10:59:42 +0300 [thread overview]
Message-ID: <20240920080012.74405-1-mankku@gmail.com> (raw)
Hello,
We experience hanging of the guest when running a hypervisor under KVM on
VMX. The L1 guest hypervisor in this particular case is pKVM for Intel
Architecture [1]. The hang occurs when a second nested guest is launched (the
first being de-privileged host). We observed that external interrupt
vmexit would not be passed to L1, instead L0 would attempt to resume L2.
We isolated the problem to VPPR not being updated on nested vmlaunch/vmresume,
and that causes vmx_has_apicv_interrupt() in nested_vmx_enter_non_root_mode()
to miss interrupts. Updating VPPR in vmx_has_apicv_interrupt() ensures VPPR
to be up-to-date.
We don't fully understand why VPPR problem appears with pKVM-IA as L1, but not
with normal KVM as L1. On pKVM-IA some of the host functionality is moved from
vmx root to non-root, but I would appreciate if someone could clarify why
normal KVM as L1 is seemingly unaffected.
Thanks,
Markku
[1]: https://lore.kernel.org/kvm/20230312180048.1778187-1-jason.cj.chen@intel.com
Markku Ahvenjärvi (1):
KVM: nVMX: update VPPR on vmlaunch/vmresume
arch/x86/kvm/lapic.c | 9 +++++----
arch/x86/kvm/lapic.h | 1 +
arch/x86/kvm/vmx/nested.c | 5 +++--
3 files changed, 9 insertions(+), 6 deletions(-)
--
2.44.1
next reply other threads:[~2024-09-20 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 7:59 Markku Ahvenjärvi [this message]
2024-09-20 7:59 ` [PATCH 1/1] KVM: nVMX: update VPPR on vmlaunch/vmresume Markku Ahvenjärvi
2024-09-20 8:18 ` Sean Christopherson
2024-09-20 12:40 ` Markku Ahvenjärvi
2024-10-02 12:42 ` Markku Ahvenjärvi
2024-10-02 15:52 ` Sean Christopherson
2024-10-02 16:49 ` Sean Christopherson
2024-10-02 17:20 ` Sean Christopherson
2024-10-03 11:29 ` Markku Ahvenjärvi
2024-10-10 11:00 ` Chao Gao
2024-10-14 10:57 ` Markku Ahvenjärvi
2024-10-16 18:54 ` Sean Christopherson
2024-10-17 13:27 ` Chao Gao
2024-10-17 16:05 ` Sean Christopherson
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=20240920080012.74405-1-mankku@gmail.com \
--to=mankku@gmail.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=janne.karhunen@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=x86@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