From: Sean Christopherson <seanjc@google.com>
To: Jon Kohler <jon@nutanix.com>
Cc: Nikolay Borisov <nik.borisov@suse.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] KVM: nVMX: Decouple EPT RWX bits from EPT Violation protection bits
Date: Thu, 27 Feb 2025 19:51:14 +0000 [thread overview]
Message-ID: <Z8DCMpSD8kNzNPky@google.com> (raw)
In-Reply-To: <4A1B24BB-E351-4F98-8A55-F2FB9F45BBF8@nutanix.com>
On Thu, Feb 27, 2025, Jon Kohler wrote:
> > On Feb 27, 2025, at 2:34 PM, Sean Christopherson <seanjc@google.com> wrote:
> >> LGTM, but any chance we could hold this until I get the MBEC RFC out?
> >
> > No? It's definitely landing before the MBEC support, and IOM it works quite nicely
> > with the MBEC support (my diff at the bottom). I don't see any reason to delay
> > or change this cleanup.
>
> Ok no problem at all, happy to rebase on top of this when it lands.
FWIW, you don't have to wait for this to land to send your RFC. You could send
your RFC as-is; obviously I'd point out the conflict, but (a) it's an RFC and
(b) generally it's not your responsibility to anticipate conflicts.
Alternatively, and probably better in this case, would be include these patches
in your RFC, with a short message in the cover letter explaining their existence.
That said, I'm guessing I'll beat you to the punch and get this landed in
kvm-x86 next before you send the RFC :-)
next prev parent reply other threads:[~2025-02-27 19:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 0:07 [PATCH v2 0/2] KVM: VMX: Clean up EPT_VIOLATIONS_xxx #defines Sean Christopherson
2025-02-27 0:07 ` [PATCH v2 1/2] KVM: VMX: Remove EPT_VIOLATIONS_ACC_*_BIT defines Sean Christopherson
2025-02-27 0:07 ` [PATCH v2 2/2] KVM: nVMX: Decouple EPT RWX bits from EPT Violation protection bits Sean Christopherson
2025-02-27 6:52 ` Nikolay Borisov
2025-02-27 19:05 ` Jon Kohler
2025-02-27 19:34 ` Sean Christopherson
2025-02-27 19:40 ` Jon Kohler
2025-02-27 19:51 ` Sean Christopherson [this message]
2025-02-28 23:40 ` [PATCH v2 0/2] KVM: VMX: Clean up EPT_VIOLATIONS_xxx #defines 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=Z8DCMpSD8kNzNPky@google.com \
--to=seanjc@google.com \
--cc=jon@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
/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