[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150531032307.GA1603@kroah.com>
Date: Sun, 31 May 2015 12:23:07 +0900
From: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
To: KY Srinivasan <kys@...rosoft.com>
Cc: Dan Carpenter <dan.carpenter@...cle.com>,
"olaf@...fle.de" <olaf@...fle.de>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"apw@...onical.com" <apw@...onical.com>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>
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 05:41:34PM +0000, KY Srinivasan wrote:
>
>
> > -----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.
Then put that in the changelog!
Please fix up and resend the series.
thanks,
greg k-h
--
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