On May 2, 2016 09:40, "Jan Beulich" wrote:
>
> >>> On 02.05.16 at 17:35, wrote:
> > On May 2, 2016 07:12, "Jan Beulich" wrote:
> >>
> >> >>> On 29.04.16 at 20:07, wrote:
> >> > @@ -229,8 +231,15 @@ struct vm_event_write_ctrlreg {
> >> > uint64_t old_value;
> >> > };
> >> >
> >> > +struct
>>> On 02.05.16 at 17:35, wrote:
> On May 2, 2016 07:12, "Jan Beulich" wrote:
>>
>> >>> On 29.04.16 at 20:07, wrote:
>> > @@ -229,8 +231,15 @@ struct vm_event_write_ctrlreg {
>> > uint64_t old_value;
>> > };
>> >
>> > +struct vm_event_singlestep {
>> > +uint64_t gfn;
>> > +};
>> > +
>>
On May 2, 2016 07:12, "Jan Beulich" wrote:
>
> >>> On 29.04.16 at 20:07, wrote:
> > @@ -229,8 +231,15 @@ struct vm_event_write_ctrlreg {
> > uint64_t old_value;
> > };
> >
> > +struct vm_event_singlestep {
> > +uint64_t gfn;
> > +};
> > +
> > struct vm_event_debug {
> > uint64_t g
>>> On 29.04.16 at 20:07, wrote:
> @@ -229,8 +231,15 @@ struct vm_event_write_ctrlreg {
> uint64_t old_value;
> };
>
> +struct vm_event_singlestep {
> +uint64_t gfn;
> +};
> +
> struct vm_event_debug {
> uint64_t gfn;
> +uint8_t type;/* HVMOP_TRAP_* */
> +uint8_t
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
