On Fri, May 29, 2015 at 05:41:34PM +0000, KY Srinivasan wrote: > > > > -----Original Message----- > > From: Dan Carpenter [mailto:dan.carpen...@oracle.com] > > Sent: Friday, May 29, 2015 10:00 AM > > To: KY Srinivasan > > Cc: gre...@linuxfoundation.org; linux-ker...@vger.kernel.org; > > de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com; > > vkuzn...@redhat.com; jasow...@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.
Then put that in the changelog! Please fix up and resend the series. thanks, greg k-h _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
