[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<155d4e72266096e0fa125b11e3bde04d8788e41a.camel@cyberus-technology.de>
Date: Wed, 8 May 2024 13:27:55 +0000
From: Thomas Prescher <thomas.prescher@...erus-technology.de>
To: "seanjc@...gle.com" <seanjc@...gle.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"x86@...nel.org" <x86@...nel.org>, "dave.hansen@...ux.intel.com"
<dave.hansen@...ux.intel.com>, "hpa@...or.com" <hpa@...or.com>, Julian
Stecklina <julian.stecklina@...erus-technology.de>, "tglx@...utronix.de"
<tglx@...utronix.de>, "bp@...en8.de" <bp@...en8.de>, "mingo@...hat.com"
<mingo@...hat.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>,
"kvm@...r.kernel.org" <kvm@...r.kernel.org>
Subject: Re: [PATCH 1/2] KVM: nVMX: fix CR4_READ_SHADOW when L0 updates CR4
during a signal
On Thu, 2024-04-18 at 11:28 -0700, Sean Christopherson wrote:
> > Allright. I will propose a patch that sets the
> > KVM_RUN_X86_GUEST_MODE
> > flag in the next couple of days. Do we also need a new capability
> > for
> > this flag so userland can query whether this field is actually
> > updated
> > by KVM?
>
> Hmm, yeah, I don't see any way around that.
Hi Sean,
we have submitted a new patch:
https://lore.kernel.org/kvm/20240508132502.184428-1-julian.stecklina@cyberus-technology.de/T/#u
Powered by blists - more mailing lists