On Mon, May 30, 2016 at 4:13 AM, Jan Beulich <jbeul...@suse.com> wrote: >>>> On 30.05.16 at 09:13, <rcojoc...@bitdefender.com> wrote: >> On 05/13/2016 02:35 PM, Jan Beulich wrote: >>>>>> On 06.05.16 at 16:33, <rcojoc...@bitdefender.com> wrote: >>>> Previously, subscribing to MSR write events was an all-or-none >>>> approach, with special cases for introspection MSR-s. This patch >>>> allows the vm_event consumer to specify exactly what MSR-s it is >>>> interested in, and as a side-effect gets rid of the >>>> vmx_introspection_force_enabled_msrs[] special case. >>>> The patch also introduces arch_monitor_init_domain() and >>>> arch_monitor_cleanup_domain(), to do monitor-specific work >>>> (as opposed to the previous way of doing all the setup in >>>> vm_event_init_domain() / vm_event_cleanup_domain()). >>>> This replaces the previously posted "xen: Filter out MSR write >>>> events" patch. >>>> >>>> Signed-off-by: Razvan Cojocaru <rcojoc...@bitdefender.com> >>>> Acked-by: Wei Liu <wei.l...@citrix.com> >>>> Acked-by: Kevin Tian <kevin.t...@intel.com> >>> >>> Acked-by: Jan Beulich <jbeul...@suse.com> >> >> Does this patch require additional acks? Tamas' maybe? > > Yes, quite clearly (looking at the diffstat).
Hm, I thought I already acked it. Acked-by: Tamas K Lengyel <ta...@tklengyel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
