Re: [PATCH V6] vm_event: Allow subscribing to write events for specific MSR-s

[Wei Liu <wei.liu2@citrix.com>]

On Wed, Apr 27, 2016 at 10:48:04AM +0300, Razvan Cojocaru 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 <rcojocaru@bitdefender.com>
> 
> ---
> Changes since V5:
>  - Modified patch description to mention the new monitor functions.
>  - Fixed duplicated xzalloc() / xfree() code.
>  - Moved the monitor setup code (memset()s from vm_event_init_domain()
>    to arch_monitor_init_domain().
>  - Now returning 0 from arch_monitor_init_domain() for ARM.
>  - No longer xzalloc()ating d->arch.monitor_msr_bitmap unless it's
>    NULL.
> ---
>  tools/libxc/include/xenctrl.h      |   9 ++-
>  tools/libxc/xc_monitor.c           |   6 +-

The changes to libxc are just plumbing, so with appropriate acks from HV
side:

Acked-by: Wei Liu <wei.liu2@citrix.com>

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel