> -----Original Message----- > From: Greg KH [mailto:gregkh@xxxxxxxxxxxxxxxxxxx] > Sent: Wednesday, February 13, 2013 11:22 AM > To: KY Srinivasan > Cc: H. Peter Anvin; 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 Wed, Feb 13, 2013 at 02:07:52PM +0000, KY Srinivasan wrote: > > > > > > > -----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? > > > > Greg, > > > > 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. > > What is "this version"? I looked at the tree that Peter checked in the patches: https://git.kernel.org/?p=linux/kernel/git/tip/tip.git;a=shortlog;h=refs/heads/x86/hyperv The code under drivers/hv is not the current tip code in your tree. That is the reason, I don't think this patch: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts should go into Peter's tree. > > > 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. > > Those are in the char-misc git tree and will to go Linus for 3.9-rc1. The patches that Peter checked in have no dependence on the vmbus patches that you have checked into 3.9-rc1. My question was with regards to how the patches that Peter has checked in to 3.8-rc7 will be merged into 3.9-rc1. If the patches that Peter checked are going to show up in 3.9 rc1, then that would be perfect. > > > Now that Peter has checked in the needed patches, could you take this > > patch through your tree. > > What again is "this"? "this" is the current patch in this email: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts As noted earlier, this patch requires the patches that Peter has now checked into 3.8 rc7. If these are going to be merged with 3.9-rc1, then you can pick up the patch titled: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts > > > Let me know, if you need, I can re-send this patch to you. > > Will it cause build problems if I take this patch in my tree, without > the changes in the -tip tree? You need to first pick up the patches that Peter has check in. Regards, K. Y _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
