[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 4 Apr 2017 19:54:33 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Bjorn Helgaas <helgaas@...nel.org>
CC: "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.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>,
"leann.ogasawara@...onical.com" <leann.ogasawara@...onical.com>,
"marcelo.cerri@...onical.com" <marcelo.cerri@...onical.com>,
Stephen Hemminger <sthemmin@...rosoft.com>
Subject: RE: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes
> -----Original Message-----
> From: Bjorn Helgaas [mailto:helgaas@...nel.org]
> Sent: Tuesday, April 4, 2017 12:04 PM
> To: KY Srinivasan <kys@...rosoft.com>
> Cc: linux-pci@...r.kernel.org; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> vkuznets@...hat.com; jasowang@...hat.com;
> leann.ogasawara@...onical.com; marcelo.cerri@...onical.com; Stephen
> Hemminger <sthemmin@...rosoft.com>
> Subject: Re: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes
>
> On Fri, Mar 24, 2017 at 11:06:40AM -0700, kys@...hange.microsoft.com
> wrote:
> > From: K. Y. Srinivasan <kys@...rosoft.com>
> >
> > Some miscellaneous fixes.
> >
> > K. Y. Srinivasan (2):
> > pci-hyperv: Fix a bug in specifying CPU affinity
> > pci-hyperv: Fix an atomic bug
> >
> > drivers/pci/host/pci-hyperv.c | 13 +++++++++----
> > 1 files changed, 9 insertions(+), 4 deletions(-)
>
> I applied these with Long's reviewed-by to pci/host-hv for v4.12 with the
> following subject lines:
>
> PCI: hv: Specify CPU_AFFINITY_ALL for MSI affinity when >= 32 CPUs
> PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC
>
Thank you.
> There were two copies of [1/2], which makes this error-prone. I applied
> the second one that defines CPU_AFFINITY_ALL.
Thanks again; sorry for the confusion.
>
> They're both marked for stable, but without any clue about when the
> problems were introduced or how serious they are, I did not queue them for
> v4.11. If you want them in v4.11, please supply those additional details.
I think these issues have been there since the driver got merged upstream.
I would want this to be applied against 4.11 as well. Let me know if I should resend
these patches.
Thanks,
K. Y
>
> Bjorn
Powered by blists - more mailing lists