From: Thomas Prescher <thomas.prescher@cyberus-technology.de>
To: "seanjc@google.com" <seanjc@google.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"hpa@zytor.com" <hpa@zytor.com>,
Julian Stecklina <julian.stecklina@cyberus-technology.de>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"bp@alien8.de" <bp@alien8.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 1/2] KVM: nVMX: fix CR4_READ_SHADOW when L0 updates CR4 during a signal
Date: Wed, 8 May 2024 13:27:55 +0000 [thread overview]
Message-ID: <155d4e72266096e0fa125b11e3bde04d8788e41a.camel@cyberus-technology.de> (raw)
In-Reply-To: <ZiFmNmlUxfQnXIua@google.com>
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
next prev parent reply other threads:[~2024-05-08 13:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 12:35 [PATCH 1/2] KVM: nVMX: fix CR4_READ_SHADOW when L0 updates CR4 during a signal Julian Stecklina
2024-04-16 12:35 ` [PATCH 2/2] KVM: nVMX: remove unnecessary CR4_READ_SHADOW write Julian Stecklina
2024-04-16 14:35 ` [PATCH 1/2] KVM: nVMX: fix CR4_READ_SHADOW when L0 updates CR4 during a signal Sean Christopherson
2024-04-16 15:08 ` Thomas Prescher
2024-04-16 15:17 ` Sean Christopherson
2024-04-16 17:31 ` Thomas Prescher
2024-04-16 18:07 ` Sean Christopherson
2024-04-17 13:05 ` Thomas Prescher
2024-04-17 16:11 ` Sean Christopherson
2024-04-17 16:28 ` Sean Christopherson
2024-04-18 13:48 ` Thomas Prescher
2024-04-18 18:28 ` Sean Christopherson
2024-05-08 13:27 ` Thomas Prescher [this message]
2024-04-18 13:46 ` Thomas Prescher
2024-04-18 18:36 ` 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=155d4e72266096e0fa125b11e3bde04d8788e41a.camel@cyberus-technology.de \
--to=thomas.prescher@cyberus-technology.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=julian.stecklina@cyberus-technology.de \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).