[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY2PR0301MB071147A5C3973C58873C63DDA0C90@BY2PR0301MB0711.namprd03.prod.outlook.com>
Date: Fri, 29 May 2015 17:41:34 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.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>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>
Subject: RE: [PATCH 1/3] Drivers: hv: vmbus: Use the vp_index map even for
channels bound to CPU 0
> -----Original Message-----
> From: Dan Carpenter [mailto:dan.carpenter@...cle.com]
> Sent: Friday, May 29, 2015 10:00 AM
> To: KY Srinivasan
> Cc: gregkh@...uxfoundation.org; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> vkuznets@...hat.com; jasowang@...hat.com
> Subject: Re: [PATCH 1/3] Drivers: hv: vmbus: Use the vp_index map even for
> channels bound to CPU 0
>
> On Fri, May 29, 2015 at 11:09:02AM -0700, K. Y. Srinivasan wrote:
> > Map target_cpu to target_vcpu using the mapping table.
> >
>
> It's really hard to tell from this changelog what the user visible
> effects of this patch are.
We should use the map to transform guest CPU ID to VP Index as is done
For the non-performance critical channels. While the value CPU 0 is special and will
map to VP index 0, it is good to be consistent.
Regards,
K. Y
>
> regards,
> dan carpenter
--
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