From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
jasowang@redhat.com, tglx@linutronix.de, hpa@zytor.com,
JBeulich@suse.com, bp@alien8.de
Subject: Re: [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts
Date: Wed, 6 Feb 2013 11:13:13 -0800 [thread overview]
Message-ID: <20130206191313.GA1470@kroah.com> (raw)
In-Reply-To: <1360164359-12273-1-git-send-email-kys@microsoft.com>
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@linuxfoundation.org>
next prev parent reply other threads:[~2013-02-06 19:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 15:25 [PATCH 1/1] Drivers: hv: vmbus: Use the new infrastructure for delivering VMBUS interrupts K. Y. Srinivasan
2013-02-06 19:13 ` Greg KH [this message]
2013-02-09 14:09 ` KY Srinivasan
2013-02-13 0:30 ` H. Peter Anvin
2013-02-13 0:43 ` KY Srinivasan
2013-02-13 0:46 ` H. Peter Anvin
2013-02-13 0:50 ` KY Srinivasan
2013-02-13 0:59 ` H. Peter Anvin
2013-02-13 14:07 ` KY Srinivasan
2013-02-13 16:22 ` Greg KH
2013-02-13 17:08 ` KY Srinivasan
2013-02-13 18:19 ` H. Peter Anvin
2013-02-13 18:23 ` Greg KH
2013-02-13 18:33 ` KY Srinivasan
2013-02-13 18:36 ` H. Peter Anvin
2013-02-13 18:52 ` Greg KH
2013-02-17 18:13 ` KY Srinivasan
2013-02-17 18:25 ` Greg KH
2013-02-17 18:51 ` KY Srinivasan
2013-02-17 19:15 ` H. Peter Anvin
2013-02-17 19:30 K. Y. Srinivasan
2013-02-27 14:39 ` KY Srinivasan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130206191313.GA1470@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=JBeulich@suse.com \
--cc=apw@canonical.com \
--cc=bp@alien8.de \
--cc=devel@linuxdriverproject.org \
--cc=hpa@zytor.com \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).