On Thu, Apr 28, 2016 at 8:29 PM, Tian, Kevin 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 a
> 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_breakpo
On Wed, Apr 27, 2016 at 11:57 PM, Razvan Cojocaru wrote:
> On 04/27/16 23:33, Tamas K Lengyel wrote:
> > 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 h
On 04/27/16 23:33, Tamas K Lengyel wrote:
> 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
> match the variou
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
match the various events that can be passed with it. We also intro
