mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Nikolay Borisov <nik.borisov@suse.com>,
	Jon Kohler <jon@nutanix.com>
Subject: Re: [PATCH v2 0/2] KVM: VMX: Clean up EPT_VIOLATIONS_xxx #defines
Date: Fri, 28 Feb 2025 15:40:36 -0800	[thread overview]
Message-ID: <174076284903.3736676.15512557789337547717.b4-ty@google.com> (raw)
In-Reply-To: <20250227000705.3199706-1-seanjc@google.com>

On Wed, 26 Feb 2025 16:07:03 -0800, Sean Christopherson wrote:
> Nikolay's patch[v1] to drop the ACC_*_BIT defines, plus another patch to
> add proper defines for the protection bits instead of piggybacking the
> RWX EPT entry defines.
> 
> v1: https://lore.kernel.org/all/20250226074151.312588-1-nik.borisov@suse.com
> 
> Nikolay Borisov (1):
>   KVM: VMX: Remove EPT_VIOLATIONS_ACC_*_BIT defines
> 
> [...]

Applied to kvm-x86 vmx, thanks!

[1/2] KVM: VMX: Remove EPT_VIOLATIONS_ACC_*_BIT defines
      https://github.com/kvm-x86/linux/commit/fa6c8fc2d267
[2/2] KVM: nVMX: Decouple EPT RWX bits from EPT Violation protection bits
      https://github.com/kvm-x86/linux/commit/61146f67e4cb

--
https://github.com/kvm-x86/linux/tree/next

      parent reply	other threads:[~2025-02-28 23:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27  0:07 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
2025-02-28 23:40 ` Sean Christopherson [this message]

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=174076284903.3736676.15512557789337547717.b4-ty@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

all inboxes | Powered by JetHome®