On Thu, Apr 28, 2016 at 8:29 PM, Tian, Kevin <kevin.t...@intel.com> wrote:
> > 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? > Thanks, already changed the name for v2 to be hvm_monitor_debug (with a precursor patch renaming hvm/event to hvm/monitor). Tamas
_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
