From: KY Srinivasan <kys@microsoft.com>
To: KY Srinivasan <kys@microsoft.com>,
"x86@kernel.org" <x86@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"apw@canonical.com" <apw@canonical.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: RE: [PATCH 1/1] Drivers: hv: Bind all vmbbus interrupts to the boot CPU
Date: Fri, 18 Jan 2013 17:27:09 +0000 [thread overview]
Message-ID: <cf0b89ceb5d34a598c500b6bbbcd5e8e@SN2PR03MB061.namprd03.prod.outlook.com> (raw)
In-Reply-To: <1358485251-13801-1-git-send-email-kys@microsoft.com>
> -----Original Message-----
> From: K. Y. Srinivasan [mailto:kys@microsoft.com]
> Sent: Friday, January 18, 2013 12:01 AM
> To: x86@kernel.org; gregkh@linuxfoundation.org; linux-kernel@vger.kernel.org;
> devel@linuxdriverproject.org; olaf@aepfle.de; apw@canonical.com;
> jasowang@redhat.com; tglx@linutronix.de
> Cc: KY Srinivasan
> Subject: [PATCH 1/1] Drivers: hv: Bind all vmbbus interrupts to the boot CPU
>
> The default interrupt delivery model in Linux does not support the Hyper-V
> vmbus delivery model when the guest is configured with multiple VCPUs. I have
> sent a patch to address this - delivering the vmbus interrupt on a separate
> IDT vector. Until this patch is applied, bind all vmbus interrupts to the boot
> CPU.
>
> Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
> ---
> drivers/hv/channel_mgmt.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/hv/channel_mgmt.c b/drivers/hv/channel_mgmt.c
> index c80fe62..7478ef9 100644
> --- a/drivers/hv/channel_mgmt.c
> +++ b/drivers/hv/channel_mgmt.c
> @@ -337,7 +337,7 @@ static u32 get_vp_index(uuid_le *type_guid)
> return 0;
> }
> cur_cpu = (++next_vp % max_cpus);
> - return hv_context.vp_index[cur_cpu];
> + return 0;
> }
Greg,
Please apply this patch. This temporary restriction will be removed once the Hyper-V IDT
Patch (or some variant of that) is applied.
Regards,
K. Y
>
> /*
> --
> 1.7.4.1
>
>
prev parent reply other threads:[~2013-01-18 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 5:00 K. Y. Srinivasan
2013-01-18 17:27 ` KY Srinivasan [this message]
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=cf0b89ceb5d34a598c500b6bbbcd5e8e@SN2PR03MB061.namprd03.prod.outlook.com \
--to=kys@microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.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
all inboxes | Powered by JetHome®