From: KY Srinivasan <kys@microsoft.com> To: Bjorn Helgaas <helgaas@kernel.org> Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>, "olaf@aepfle.de" <olaf@aepfle.de>, "apw@canonical.com" <apw@canonical.com>, "vkuznets@redhat.com" <vkuznets@redhat.com>, "jasowang@redhat.com" <jasowang@redhat.com>, "leann.ogasawara@canonical.com" <leann.ogasawara@canonical.com>, "marcelo.cerri@canonical.com" <marcelo.cerri@canonical.com>, Stephen Hemminger <sthemmin@microsoft.com> Subject: RE: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes Date: Tue, 4 Apr 2017 19:54:33 +0000 [thread overview] Message-ID: <DM5PR03MB249052D8580711F8999048D8A00B0@DM5PR03MB2490.namprd03.prod.outlook.com> (raw) In-Reply-To: <20170404190331.GD27692@bhelgaas-glaptop.roam.corp.google.com> > -----Original Message----- > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > Sent: Tuesday, April 4, 2017 12:04 PM > To: KY Srinivasan <kys@microsoft.com> > Cc: linux-pci@vger.kernel.org; linux-kernel@vger.kernel.org; > devel@linuxdriverproject.org; olaf@aepfle.de; apw@canonical.com; > vkuznets@redhat.com; jasowang@redhat.com; > leann.ogasawara@canonical.com; marcelo.cerri@canonical.com; Stephen > Hemminger <sthemmin@microsoft.com> > Subject: Re: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes > > On Fri, Mar 24, 2017 at 11:06:40AM -0700, kys@exchange.microsoft.com > wrote: > > From: K. Y. Srinivasan <kys@microsoft.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
WARNING: multiple messages have this Message-ID (diff)
From: KY Srinivasan <kys@microsoft.com> To: Bjorn Helgaas <helgaas@kernel.org> Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "devel@linuxdriverproject.org" <devel@linuxdriverproject.org>, "olaf@aepfle.de" <olaf@aepfle.de>, "apw@canonical.com" <apw@canonical.com>, "vkuznets@redhat.com" <vkuznets@redhat.com>, "jasowang@redhat.com" <jasowang@redhat.com>, "leann.ogasawara@canonical.com" <leann.ogasawara@canonical.com>, "marcelo.cerri@canonical.com" <marcelo.cerri@canonical.com>, Stephen Hemminger <sthemmin@microsoft.com> Subject: RE: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes Date: Tue, 4 Apr 2017 19:54:33 +0000 [thread overview] Message-ID: <DM5PR03MB249052D8580711F8999048D8A00B0@DM5PR03MB2490.namprd03.prod.outlook.com> (raw) In-Reply-To: <20170404190331.GD27692@bhelgaas-glaptop.roam.corp.google.com> > -----Original Message----- > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > Sent: Tuesday, April 4, 2017 12:04 PM > To: KY Srinivasan <kys@microsoft.com> > Cc: linux-pci@vger.kernel.org; linux-kernel@vger.kernel.org; > devel@linuxdriverproject.org; olaf@aepfle.de; apw@canonical.com; > vkuznets@redhat.com; jasowang@redhat.com; > leann.ogasawara@canonical.com; marcelo.cerri@canonical.com; Stephen > Hemminger <sthemmin@microsoft.com> > Subject: Re: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes >=20 > On Fri, Mar 24, 2017 at 11:06:40AM -0700, kys@exchange.microsoft.com > wrote: > > From: K. Y. Srinivasan <kys@microsoft.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(-) >=20 > I applied these with Long's reviewed-by to pci/host-hv for v4.12 with the > following subject lines: >=20 > PCI: hv: Specify CPU_AFFINITY_ALL for MSI affinity when >=3D 32 CPUs > PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC >=20 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. >=20 > 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 fo= r > 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 shou= ld resend these patches. Thanks, K. Y=20 >=20 > Bjorn
next prev parent reply other threads:[~2017-04-04 19:54 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-03-24 18:06 [PATCH 0/2] pci-hyperv: Some miscellaneous fixes kys 2017-03-24 18:07 ` [PATCH 1/2] PCI: hv: Fix a bug in specifying CPU affinity kys 2017-03-24 18:07 ` [PATCH 1/2] pci-hyperv: " kys 2017-03-27 18:13 ` Long Li 2017-03-27 18:13 ` Long Li 2017-03-24 18:07 ` [PATCH 2/2] pci-hyperv: Fix an atomic bug kys 2017-03-27 18:14 ` Long Li 2017-03-27 18:14 ` Long Li 2017-04-04 19:03 ` [PATCH 0/2] pci-hyperv: Some miscellaneous fixes Bjorn Helgaas 2017-04-04 19:54 ` KY Srinivasan [this message] 2017-04-04 19:54 ` KY Srinivasan 2017-04-04 20:39 ` Bjorn Helgaas 2017-04-04 21:47 ` KY Srinivasan 2017-04-04 21:47 ` KY Srinivasan
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=DM5PR03MB249052D8580711F8999048D8A00B0@DM5PR03MB2490.namprd03.prod.outlook.com \ --to=kys@microsoft.com \ --cc=apw@canonical.com \ --cc=devel@linuxdriverproject.org \ --cc=helgaas@kernel.org \ --cc=jasowang@redhat.com \ --cc=leann.ogasawara@canonical.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=marcelo.cerri@canonical.com \ --cc=olaf@aepfle.de \ --cc=sthemmin@microsoft.com \ --cc=vkuznets@redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.