From: Peter Xu <peterx@redhat.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: peterx@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Andrew Jones <drjones@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: [PATCH v14 01/14] KVM: Documentation: Update entry for KVM_X86_SET_MSR_FILTER
Date: Wed, 7 Oct 2020 16:53:29 -0400 [thread overview]
Message-ID: <20201007205342.295402-2-peterx@redhat.com> (raw)
In-Reply-To: <20201007205342.295402-1-peterx@redhat.com>
It should be an accident when rebase, since we've already have section
8.25 (which is KVM_CAP_S390_DIAG318). Fix the number.
Signed-off-by: Peter Xu <peterx@redhat.com>
---
Documentation/virt/kvm/api.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst
index 425325ff4434..136b11007d74 100644
--- a/Documentation/virt/kvm/api.rst
+++ b/Documentation/virt/kvm/api.rst
@@ -6360,7 +6360,7 @@ accesses that would usually trigger a #GP by KVM into the guest will
instead get bounced to user space through the KVM_EXIT_X86_RDMSR and
KVM_EXIT_X86_WRMSR exit notifications.
-8.25 KVM_X86_SET_MSR_FILTER
+8.27 KVM_X86_SET_MSR_FILTER
---------------------------
:Architectures: x86
--
2.26.2
next prev parent reply other threads:[~2020-10-07 20:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 20:53 [PATCH v14 00/14] KVM: Dirty ring interface Peter Xu
2020-10-07 20:53 ` Peter Xu [this message]
2020-10-07 20:53 ` [PATCH v14 02/14] KVM: Cache as_id in kvm_memory_slot Peter Xu
2020-10-07 20:53 ` [PATCH v14 03/14] KVM: X86: Don't track dirty for KVM_SET_[TSS_ADDR|IDENTITY_MAP_ADDR] Peter Xu
2020-10-07 20:53 ` [PATCH v14 04/14] KVM: Pass in kvm pointer into mark_page_dirty_in_slot() Peter Xu
2020-10-07 20:53 ` [PATCH v14 05/14] KVM: X86: Implement ring-based dirty memory tracking Peter Xu
2020-10-07 20:53 ` [PATCH v14 06/14] KVM: Make dirty ring exclusive to dirty bitmap log Peter Xu
2020-10-07 20:53 ` [PATCH v14 07/14] KVM: Don't allocate dirty bitmap if dirty ring is enabled Peter Xu
2020-10-07 20:53 ` [PATCH v14 08/14] KVM: selftests: Always clear dirty bitmap after iteration Peter Xu
2020-10-07 20:53 ` [PATCH v14 09/14] KVM: selftests: Sync uapi/linux/kvm.h to tools/ Peter Xu
2020-10-07 20:53 ` [PATCH v14 10/14] KVM: selftests: Use a single binary for dirty/clear log test Peter Xu
2020-10-07 20:53 ` [PATCH v14 11/14] KVM: selftests: Introduce after_vcpu_run hook for dirty " Peter Xu
2020-10-07 20:53 ` [PATCH v14 12/14] KVM: selftests: Add dirty ring buffer test Peter Xu
2020-10-07 20:53 ` [PATCH v14 13/14] KVM: selftests: Let dirty_log_test async for dirty ring test Peter Xu
2020-10-07 20:53 ` [PATCH v14 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=20201007205342.295402-2-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).