From: "Markku Ahvenjärvi" <mankku@gmail.com>
To: seanjc@google.com
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
janne.karhunen@gmail.com, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, mankku@gmail.com, mingo@redhat.com,
pbonzini@redhat.com, tglx@linutronix.de, x86@kernel.org
Subject: Re: [PATCH 1/1] KVM: nVMX: update VPPR on vmlaunch/vmresume
Date: Fri, 20 Sep 2024 15:40:29 +0300 [thread overview]
Message-ID: <20240920124414.26988-1-mankku@gmail.com> (raw)
In-Reply-To: <Zu0vvRyCyUaQ2S2a@google.com>
> This is architecturally incorrect, PPR isn't refreshed at VM-Enter.
Ah, I see. Thanks for pointing out.
> Aha! I wonder if the missing PPR update is due to the nested VM-Enter path
> directly clearing IRR when processing a posted interrupt.
>
> On top of https://github.com/kvm-x86/linux/tree/next, does this fix things?
>
> diff --git a/arch/x86/kvm/vmx/nested.c b/arch/x86/kvm/vmx/nested.c
> index a8e7bc04d9bf..a8255c6f0d51 100644
> --- a/arch/x86/kvm/vmx/nested.c
> +++ b/arch/x86/kvm/vmx/nested.c
> @@ -3731,7 +3731,7 @@ static int nested_vmx_run(struct kvm_vcpu *vcpu, bool launch)
> kvm_apic_has_interrupt(vcpu) == vmx->nested.posted_intr_nv) {
> vmx->nested.pi_pending = true;
> kvm_make_request(KVM_REQ_EVENT, vcpu);
> - kvm_apic_clear_irr(vcpu, vmx->nested.posted_intr_nv);
> + kvm_apic_ack_interrupt(vcpu, vmx->nested.posted_intr_nv);
> }
>
> /* Hide L1D cache contents from the nested guest. */
No, unfortunately.
The vmexits L1 is not receiving originate from deprivileged host (like timer
ticks), running in vmx non-root mode.
Thanks,
Markku
next prev parent reply other threads:[~2024-09-20 12:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 7:59 [PATCH 0/1] KVM: nVMX: update VPPR on vmlaunch/vmresume Markku Ahvenjärvi
2024-09-20 7:59 ` [PATCH 1/1] " Markku Ahvenjärvi
2024-09-20 8:18 ` Sean Christopherson
2024-09-20 12:40 ` Markku Ahvenjärvi [this message]
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=20240920124414.26988-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