From: guangrong.xiao@gmail.com
To: pbonzini@redhat.com, mtosatti@redhat.com, avi.kivity@gmail.com,
rkrcmar@redhat.com
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
qemu-devel@nongnu.org, Xiao Guangrong <xiaoguangrong@tencent.com>
Subject: [Qemu-devel] [PATCH v2 4/7] KVM: MMU: enable KVM_WRITE_PROTECT_ALL_MEM
Date: Tue, 20 Jun 2017 17:15:23 +0800 [thread overview]
Message-ID: <20170620091526.4287-5-xiaoguangrong@tencent.com> (raw)
In-Reply-To: <20170620091526.4287-1-xiaoguangrong@tencent.com>
From: Xiao Guangrong <xiaoguangrong@tencent.com>
The functionality of write protection for all guest memory is ready,
it is the time to make its usable for userspace which is indicated
by KVM_CAP_X86_WRITE_PROTECT_ALL_MEM
Signed-off-by: Xiao Guangrong <xiaoguangrong@tencent.com>
---
arch/x86/kvm/x86.c | 21 +++++++++++++++++++++
include/uapi/linux/kvm.h | 2 ++
2 files changed, 23 insertions(+)
diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index a2cd099..ad62c44 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -2723,6 +2723,17 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
case KVM_CAP_X2APIC_API:
r = KVM_X2APIC_API_VALID_FLAGS;
break;
+ case KVM_CAP_X86_WRITE_PROTECT_ALL_MEM:
+ /*
+ * do not enable it if PML is supported, this is also the
+ * hint to tell userspace write-protect is not needed for
+ * dirty log.
+ */
+ if (kvm_x86_ops->slot_enable_log_dirty)
+ r = 0;
+ else
+ r = 1;
+ break;
default:
r = 0;
break;
@@ -4208,6 +4219,16 @@ long kvm_arch_vm_ioctl(struct file *filp,
r = 0;
break;
}
+ case KVM_WRITE_PROTECT_ALL_MEM: {
+ if (kvm_x86_ops->slot_enable_log_dirty) {
+ r = -EINVAL;
+ break;
+ }
+
+ kvm_mmu_write_protect_all_pages(kvm, !!arg);
+ r = 0;
+ break;
+ }
case KVM_ENABLE_CAP: {
struct kvm_enable_cap cap;
diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h
index 577429a..7d4a395 100644
--- a/include/uapi/linux/kvm.h
+++ b/include/uapi/linux/kvm.h
@@ -895,6 +895,7 @@ struct kvm_ppc_resize_hpt {
#define KVM_CAP_SPAPR_TCE_VFIO 142
#define KVM_CAP_X86_GUEST_MWAIT 143
#define KVM_CAP_ARM_USER_IRQ 144
+#define KVM_CAP_X86_WRITE_PROTECT_ALL_MEM 145
#ifdef KVM_CAP_IRQ_ROUTING
@@ -1144,6 +1145,7 @@ struct kvm_vfio_spapr_tce {
struct kvm_userspace_memory_region)
#define KVM_SET_TSS_ADDR _IO(KVMIO, 0x47)
#define KVM_SET_IDENTITY_MAP_ADDR _IOW(KVMIO, 0x48, __u64)
+#define KVM_WRITE_PROTECT_ALL_MEM _IO(KVMIO, 0x49)
/* enable ucontrol for s390 */
struct kvm_s390_ucas_mapping {
--
2.9.4
next prev parent reply other threads:[~2017-06-20 9:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 9:15 [Qemu-devel] [PATCH v2 0/7] KVM: MMU: fast write protect guangrong.xiao
2017-06-20 9:15 ` [Qemu-devel] [PATCH v2 1/7] KVM: MMU: correct the behavior of mmu_spte_update_no_track guangrong.xiao
2017-06-20 9:15 ` [Qemu-devel] [PATCH v2 2/7] KVM: MMU: introduce possible_writable_spte_bitmap guangrong.xiao
2017-06-20 9:15 ` [Qemu-devel] [PATCH v2 3/7] KVM: MMU: introduce kvm_mmu_write_protect_all_pages guangrong.xiao
2017-06-20 9:15 ` guangrong.xiao [this message]
2017-06-20 9:15 ` [Qemu-devel] [PATCH v2 5/7] KVM: MMU: allow dirty log without write protect guangrong.xiao
2017-06-20 9:15 ` [Qemu-devel] [PATCH v2 6/7] KVM: MMU: clarify fast_pf_fix_direct_spte guangrong.xiao
2017-06-20 9:15 ` [Qemu-devel] [PATCH v2 7/7] KVM: MMU: stop using mmu_spte_get_lockless under mmu-lock guangrong.xiao
2017-07-03 14:39 ` [Qemu-devel] [PATCH v2 0/7] KVM: MMU: fast write protect Xiao Guangrong
2017-07-03 15:47 ` Paolo Bonzini
2017-07-04 3:17 ` Xiao Guangrong
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=20170620091526.4287-5-xiaoguangrong@tencent.com \
--to=guangrong.xiao@gmail.com \
--cc=avi.kivity@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=xiaoguangrong@tencent.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).