linux-kernel - Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts

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: <511ADEB7.6080909@zytor.com>
Date:	Tue, 12 Feb 2013 16:30:47 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	"K. Y. Srinivasan" <kys@...rosoft.com>, 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?

	-hpa


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