Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1634867

[PATCH 4/7] KVM: MMU: enable KVM_WRITE_PROTECT_ALL_MEM

From guangrong.xiao@gmail.com
Newsgroups linux.kernel
Subject [PATCH 4/7] KVM: MMU: enable KVM_WRITE_PROTECT_ALL_MEM
Date 2017-05-03 13:00 +0200
Message-ID <tD0aJ-4bC-11@gated-at.bofh.it> (permalink)
References <tD0aJ-4bC-9@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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       | 6 ++++++
 include/uapi/linux/kvm.h | 2 ++
 2 files changed, 8 insertions(+)

diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
index be2ade5..dcbeaf4 100644
--- a/arch/x86/kvm/x86.c
+++ b/arch/x86/kvm/x86.c
@@ -2669,6 +2669,7 @@ int kvm_vm_ioctl_check_extension(struct kvm *kvm, long ext)
 	case KVM_CAP_SET_BOOT_CPU_ID:
  	case KVM_CAP_SPLIT_IRQCHIP:
 	case KVM_CAP_IMMEDIATE_EXIT:
+	case KVM_CAP_X86_WRITE_PROTECT_ALL_MEM:
 		r = 1;
 		break;
 	case KVM_CAP_ADJUST_CLOCK:
@@ -4204,6 +4205,11 @@ long kvm_arch_vm_ioctl(struct file *filp,
 		r = 0;
 		break;
 	}
+	case KVM_WRITE_PROTECT_ALL_MEM: {
+		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.3

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 0/7] KVM: MMU: fast write protect guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 4/7] KVM: MMU: enable KVM_WRITE_PROTECT_ALL_MEM guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 6/7] KVM: MMU: clarify fast_pf_fix_direct_spte guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 5/7] KVM: MMU: allow dirty log without write protect guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 3/7] KVM: MMU: introduce kvm_mmu_write_protect_all_pages guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 1/7] KVM: MMU: correct the behavior of mmu_spte_update_no_track guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 7/7] KVM: MMU: stop using mmu_spte_get_lockless under mmu-lock guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  [PATCH 2/7] KVM: MMU: introduce possible_writable_spte_bitmap guangrong.xiao@gmail.com - 2017-05-03 13:00 +0200
  Re: [PATCH 0/7] KVM: MMU: fast write protect Paolo Bonzini <pbonzini@redhat.com> - 2017-05-03 14:30 +0200
    Re: [PATCH 0/7] KVM: MMU: fast write protect Xiao Guangrong <guangrong.xiao@gmail.com> - 2017-05-03 17:00 +0200
      Re: [PATCH 0/7] KVM: MMU: fast write protect Paolo Bonzini <pbonzini@redhat.com> - 2017-05-03 17:00 +0200
        Re: [PATCH 0/7] KVM: MMU: fast write protect Xiao Guangrong <guangrong.xiao@gmail.com> - 2017-05-04 05:40 +0200
          Re: [PATCH 0/7] KVM: MMU: fast write protect Paolo Bonzini <pbonzini@redhat.com> - 2017-05-04 09:10 +0200

csiph-web