search for: kvmi_

...nhook are relatively rare events and not performance critical, >> so make those the restricted/slow flows, e.g. force userspace to quiesce >> the VM by making unhook() mutually exclusive with every vcpu ioctl() and >> maybe anything that takes kvm->lock. >> >> Then kvmi_ioctl_unhook() can use thread_stop() and kvmi_recv() just needs >> to check kthread_should_stop(). >> >> That way kvmi doesn't need to be refcounted since it's guaranteed to be >> alive if the pointer is non-null. Eliminating the refcounting will clean >> up a...

...events and not performance critical, > >> so make those the restricted/slow flows, e.g. force userspace to quiesce > >> the VM by making unhook() mutually exclusive with every vcpu ioctl() and > >> maybe anything that takes kvm->lock. > >> > >> Then kvmi_ioctl_unhook() can use thread_stop() and kvmi_recv() just needs > >> to check kthread_should_stop(). > >> > >> That way kvmi doesn't need to be refcounted since it's guaranteed to be > >> alive if the pointer is non-null. Eliminating the refcounting will...

...inux/kvm_host.h > index c38cc5eb7e73..582b0187f5a4 100644 > --- a/include/linux/kvm_host.h > +++ b/include/linux/kvm_host.h > @@ -455,6 +455,10 @@ struct kvm { > struct srcu_struct srcu; > struct srcu_struct irq_srcu; > pid_t userspace_pid; > + > + struct completion kvmi_completed; > + refcount_t kvmi_ref; The refcounting approach seems a bit backwards, and AFAICT is driven by implementing unhook via a message, which also seems backwards. I assume hook and unhook are relatively rare events and not performance critical, so make those the restricted/slow flows, e...

.../kvmi/README I hope this version will be merged into KVM-VMI project too. Patches 1-20: unroll a big part of the KVM introspection subsystem, sent in one patch in the previous versions. Patches 21-24: extend the current page tracking code. Patches 25-33: make use of page tracking to support the KVMI_SET_PAGE_ACCESS introspection command and the KVMI_EVENT_PF event (on EPT violations caused by the tracking settings). Patches 34-42: include the SPP feature (Enable Sub-page Write Protection Support), already sent to KVM list: https://lore.kernel.org/lkml/20190717133751.12910-1-weijiang.yang at...

.../kvmi/README I hope this version will be merged into KVM-VMI project too. Patches 1-20: unroll a big part of the KVM introspection subsystem, sent in one patch in the previous versions. Patches 21-24: extend the current page tracking code. Patches 25-33: make use of page tracking to support the KVMI_SET_PAGE_ACCESS introspection command and the KVMI_EVENT_PF event (on EPT violations caused by the tracking settings). Patches 34-42: include the SPP feature (Enable Sub-page Write Protection Support), already sent to KVM list: https://lore.kernel.org/lkml/20190717133751.12910-1-weijiang.yang at...