[PATCH 1/3] Drivers: hv: vmbus: Use the vp_index map even for channels bound to CPU 0

KY Srinivasan kys at microsoft.com
Fri May 29 17:41:34 UTC 2015



> -----Original Message-----
> From: Dan Carpenter [mailto:dan.carpenter at oracle.com]
> Sent: Friday, May 29, 2015 10:00 AM
> To: KY Srinivasan
> Cc: gregkh at linuxfoundation.org; linux-kernel at vger.kernel.org;
> devel at linuxdriverproject.org; olaf at aepfle.de; apw at canonical.com;
> vkuznets at redhat.com; jasowang at redhat.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



More information about the devel mailing list