lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130213162211.GA21253@kroah.com>
Date:	Wed, 13 Feb 2013 08:22:11 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	KY Srinivasan <kys@...rosoft.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
	"olaf@...fle.de" <olaf@...fle.de>,
	"apw@...onical.com" <apw@...onical.com>,
	"jasowang@...hat.com" <jasowang@...hat.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"JBeulich@...e.com" <JBeulich@...e.com>,
	"bp@...en8.de" <bp@...en8.de>
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@...or.com]
> > Sent: Tuesday, February 12, 2013 7:31 PM
> > To: Greg KH
> > Cc: KY Srinivasan; x86@...nel.org; linux-kernel@...r.kernel.org;
> > devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> > jasowang@...hat.com; tglx@...utronix.de; JBeulich@...e.com; bp@...en8.de
> > 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@...uxfoundation.org>
> > >
> > 
> > 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"?

> 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.

> Now that Peter has checked in the needed patches, could you take this
> patch through your tree.

What again is "this"?

> 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?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ