> From: Tamas K Lengyel [mailto:ta...@tklengyel.com] > Sent: Thursday, April 28, 2016 4:33 AM > > Since in-guest debug exceptions are now unconditionally trapped to Xen, adding > a hook for vm_event subscribers to tap into this new always-on guest event. We > rename along the way hvm_event_breakpoint_type to hvm_event_type to better
I don't quite understand above renaming. How do you define 'event' here? There are other functions like hvm_event_msr, hvm_event_cr, etc. The new name hvm_event_type looks need to cover all those paths too? > match the various events that can be passed with it. We also introduce the > necessary monitor_op domctl's to enable subscribing to the events. > > Signed-off-by: Tamas K Lengyel <ta...@tklengyel.com> Thanks Kevin _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
