RE: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure fordelivering VMBUS interrupts

From: KY Srinivasan
Date: Wed Feb 13 2013 - 09:10:49 EST

> -----Original Message-----
> From: H. Peter Anvin [mailto:hpa@xxxxxxxxx]
> Sent: Tuesday, February 12, 2013 7:31 PM
> To: Greg KH
> Cc: KY Srinivasan; x86@xxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx; apw@xxxxxxxxxxxxx;
> jasowang@xxxxxxxxxx; tglx@xxxxxxxxxxxxx; JBeulich@xxxxxxxx; bp@xxxxxxxxx
> Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for
> delivering VMBUS interrupts
> On 02/06/2013 11:13 AM, Greg KH wrote:
> > On Wed, Feb 06, 2013 at 07:25:59AM -0800, K. Y. Srinivasan wrote:
> >> Use the infrastructure for delivering VMBUS interrupts using a
> >> special vector. With this patch, we can now properly handle
> >> the VMBUS interrupts that can be delivered on any CPU. Also,
> >> turn on interrupt load balancing as well.
> >>
> >> This patch requires the infrastructure that was implemented in the patch:
> >> X86: Handle Hyper-V vmbus interrupts as special hypervisor interrupts
> >>
> >
> > Because of the dependancy, this should go through the x86 tree as well:
> > Acked-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> >
> This does not apply to v3.8-rc7 + the set of three vmbus patches for
> x86. I take it there are additional dependencies -- K.Y., what do I
> need here?


Peter has checked in the infrastructural patches into v3.8-rc7. This version
does not have the patches that upgraded the VMBUS protocol version to the
win8 levels. How will the infrastructural patches get moved forward to the version where you
have checked-in all the vmbus protocol updates:
[PATCH 00/28] Drivers: hv: Update the Vmbus protocol.

Now that Peter has checked in the needed patches, could you take this patch through your tree.
Let me know, if you need, I can re-send this patch to you.


K. Y

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at