> -Original Message-
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: Tuesday, February 25, 2014 11:10 AM
> To: KY Srinivasan
> Cc: LKML; Ingo Molnar; Peter Zijlstra; x86; Greg Kroah-Hartman; linuxdrivers
> Subject: RE: [patch 25/26] x86: hyperv: Cleanup th
gt; linuxdrivers
> > Subject: [patch 25/26] x86: hyperv: Cleanup the irq mess
> >
> > The vmbus/hyperv interrupt handling is another complete trainwreck and
> > probably the worst of all currently in tree.
> >
> > If CONFIG_HYPERV=y then the interrupt delivery to
> -Original Message-
> From: Thomas Gleixner [mailto:t...@linutronix.de]
> Sent: Sunday, February 23, 2014 1:40 PM
> To: LKML
> Cc: Ingo Molnar; Peter Zijlstra; x86; KY Srinivasan; Greg Kroah-Hartman;
> linuxdrivers
> Subject: [patch 25/26] x86: hyperv: Cleanup
The vmbus/hyperv interrupt handling is another complete trainwreck and
probably the worst of all currently in tree.
If CONFIG_HYPERV=y then the interrupt delivery to the vmbus happens
via the direct HYPERVISOR_CALLBACK_VECTOR. So far so good, but:
The driver requests first a normal device inter
