>>> On 13.12.16 at 15:50, <rcojoc...@bitdefender.com> wrote: > Added support for a new event type, VM_EVENT_REASON_INTERRUPT, > which is now fired in a one-shot manner when enabled via the new > VM_EVENT_FLAG_GET_NEXT_INTERRUPT vm_event response flag. > The patch also fixes the behaviour of the xc_hvm_inject_trap() > hypercall, which would lead to non-architectural interrupts > overwriting pending (specifically reinjected) architectural ones. > > Signed-off-by: Razvan Cojocaru <rcojoc...@bitdefender.com> > Acked-by: Tamas K Lengyel <ta...@tklengyel.com> > Acked-by: Jan Beulich <jbeul...@suse.com> > Acked-by: Kevin Tian <kevin.t...@intel.com> > Acked-by: Suravee Suthikulpanit <suravee.suthikulpa...@amd.com> > Acked-by: Julien Grall <julien.gr...@arm.com> > > --- > Changes since V5: > - Rebased on master and re-tested.
I have to admit that I find this rather annoying: The patch still didn't apply cleanly (perhaps because you indeed did what is written above, instead of re-basing onto staging, albeit otoh I don't see how you would then have run into the build issue you reported), which again I took the time to fix up, just to find that again things don't build (for ARM at least). Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
