linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Sean Christopherson <sean.j.christopherson@intel.com>,
	peterx@redhat.com, Andrew Jones <drjones@redhat.com>,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: [PATCH v15 02/14] KVM: Documentation: Update entry for KVM_CAP_ENFORCE_PV_CPUID
Date: Fri, 23 Oct 2020 14:33:46 -0400	[thread overview]
Message-ID: <20201023183358.50607-3-peterx@redhat.com> (raw)
In-Reply-To: <20201023183358.50607-1-peterx@redhat.com>

Should be squashed into 66570e966dd9cb4f.

Signed-off-by: Peter Xu <peterx@redhat.com>
---
 Documentation/virt/kvm/api.rst | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 094e128634d2..f78307e77371 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -6381,8 +6381,7 @@ In combination with KVM_CAP_X86_USER_SPACE_MSR, this allows user space to
 trap and emulate MSRs that are outside of the scope of KVM as well as
 limit the attack surface on KVM's MSR emulation code.
 
-
-8.26 KVM_CAP_ENFORCE_PV_CPUID
+8.28 KVM_CAP_ENFORCE_PV_CPUID
 -----------------------------
 
 Architectures: x86
-- 
2.26.2


  parent reply	other threads:[~2020-10-23 18:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-23 18:33 [PATCH v15 00/14] KVM: Dirty ring interface Peter Xu
2020-10-23 18:33 ` [PATCH v15 01/14] KVM: Documentation: Update entry for KVM_X86_SET_MSR_FILTER Peter Xu
2020-10-23 18:33 ` Peter Xu [this message]
2020-10-23 18:33 ` [PATCH v15 03/14] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR] Peter Xu
2020-10-23 18:33 ` [PATCH v15 04/14] KVM: Pass in kvm pointer into mark_page_dirty_in_slot() Peter Xu
2020-10-23 18:33 ` [PATCH v15 05/14] KVM: X86: Implement ring-based dirty memory tracking Peter Xu
2020-10-23 18:33 ` [PATCH v15 06/14] KVM: Make dirty ring exclusive to dirty bitmap log Peter Xu
2020-10-23 18:33 ` [PATCH v15 07/14] KVM: Don't allocate dirty bitmap if dirty ring is enabled Peter Xu
2020-10-23 18:33 ` [PATCH v15 08/14] KVM: selftests: Always clear dirty bitmap after iteration Peter Xu
2020-10-23 18:33 ` [PATCH v15 09/14] KVM: selftests: Sync uapi/linux/kvm.h to tools/ Peter Xu
2020-10-23 18:33 ` [PATCH v15 10/14] KVM: selftests: Use a single binary for dirty/clear log test Peter Xu
2020-10-23 18:33 ` [PATCH v15 11/14] KVM: selftests: Introduce after_vcpu_run hook for dirty " Peter Xu
2020-10-23 18:33 ` [PATCH v15 12/14] KVM: selftests: Add dirty ring buffer test Peter Xu
2020-10-23 18:33 ` [PATCH v15 13/14] KVM: selftests: Let dirty_log_test async for dirty ring test Peter Xu
2020-10-23 18:33 ` [PATCH v15 14/14] KVM: selftests: Add "-c" parameter to dirty log test Peter Xu

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=20201023183358.50607-3-peterx@redhat.com \
    --to=peterx@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=sean.j.christopherson@intel.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;
as well as URLs for NNTP newsgroup(s).