From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754765AbdDDVrz (ORCPT ); Tue, 4 Apr 2017 17:47:55 -0400 Received: from mail-by2nam01on0129.outbound.protection.outlook.com ([104.47.34.129]:5312 "EHLO NAM01-BY2-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754090AbdDDVrw (ORCPT ); Tue, 4 Apr 2017 17:47:52 -0400 From: KY Srinivasan To: Bjorn Helgaas 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 Subject: RE: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes Thread-Topic: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes Thread-Index: AQHSpMmKvQcA1nZCgEO6BA0G7ITUJKG1ormAgAAIAcCAABLPgIAAEmDQ Date: Tue, 4 Apr 2017 21:47:39 +0000 Message-ID: References: <1490378800-26907-1-git-send-email-kys@exchange.microsoft.com> <20170404190331.GD27692@bhelgaas-glaptop.roam.corp.google.com> <20170404203929.GF27692@bhelgaas-glaptop.roam.corp.google.com> In-Reply-To: <20170404203929.GF27692@bhelgaas-glaptop.roam.corp.google.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: kernel.org; dkim=none (message not signed) header.d=none;kernel.org; dmarc=none action=none header.from=microsoft.com; x-originating-ip: [2001:4898:80e8:4::344] x-microsoft-exchange-diagnostics: 1;BY2PR0301MB2104;7:LwT9x5+Em78LH474liH90AOL4A/JDMl0o4oHE+y2evDpMlmsjnmAOBjUmM66g786G1tX7ayjUqD/4bkWuZeaPO+3tgKOLqW2Qzw041wn7DD6R3yM6Qv/JuzRm838+5ENwhfLK+N+lI9H2qb3x0y4dc6im523evC70nh1GXrEXQriYtkvcsLzsWASCfE1kJLyKdgRQsnMIIo3/F2cHQZDs1y9XmtNuVMyhAdOVVAHQ/n36yJ1SyqDSzQeylrNcEPEvJG/Jo9zVKriiOivCJMJFafboudH2A2WA7VEezwDU1dq/ZQbr9pZM7oSTXJMr3z6IFxu317TDwGhckS/Bfw5kt+igEdeM/a3K90NWhQ2YRs= x-ms-office365-filtering-correlation-id: 226b8919-eb9a-470c-bfa6-08d47ba4376e x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);SRVR:BY2PR0301MB2104; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(9452136761055)(140211028294663)(198206253151910); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123555025)(6072148);SRVR:BY2PR0301MB2104;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0301MB2104; x-forefront-prvs: 0267E514F9 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(39450400003)(39410400002)(39850400002)(39400400002)(39860400002)(39840400002)(377454003)(43784003)(24454002)(13464003)(229853002)(6246003)(53936002)(53546009)(77096006)(5005710100001)(10290500002)(8990500004)(305945005)(7416002)(81166006)(33656002)(8676002)(8936002)(7736002)(10090500001)(93886004)(74316002)(2950100002)(7696004)(6916009)(5660300001)(110136004)(38730400002)(107886003)(25786009)(122556002)(86362001)(189998001)(4326008)(2906002)(2900100001)(3280700002)(3660700001)(102836003)(6116002)(6506006)(6436002)(50986999)(54906002)(76176999)(9686003)(99286003)(54356999)(55016002);DIR:OUT;SFP:1102;SCL:1;SRVR:BY2PR0301MB2104;H:DM5PR03MB2490.namprd03.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2017 21:47:39.9158 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0301MB2104 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id v34Llx37016683 > -----Original Message----- > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > Sent: Tuesday, April 4, 2017 1:39 PM > To: KY Srinivasan > 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 > Subject: Re: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes > > On Tue, Apr 04, 2017 at 07:54:33PM +0000, KY Srinivasan wrote: > > > -----Original Message----- > > > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > > > Sent: Tuesday, April 4, 2017 12:04 PM > > > To: KY Srinivasan > > > 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 > > > 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 > > > > > > > > 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. > > No need to resend, but I do need more details about what issues these fix > and why they're more urgent than garden-variety bug fixes that are planned > for v4.12. In general for-linus is for fixing problems we added during the > merge window, or other high-priority, low-risk changes. For sure I want to get this into 4.12. Since it fixes issues that have been there for a long time, (including 4.11), it would be good to get it into 4.11 as well. Regards, K. Y > > Bjorn From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: KY Srinivasan To: Bjorn Helgaas 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 Subject: RE: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes Date: Tue, 4 Apr 2017 21:47:39 +0000 Message-ID: References: <1490378800-26907-1-git-send-email-kys@exchange.microsoft.com> <20170404190331.GD27692@bhelgaas-glaptop.roam.corp.google.com> <20170404203929.GF27692@bhelgaas-glaptop.roam.corp.google.com> In-Reply-To: <20170404203929.GF27692@bhelgaas-glaptop.roam.corp.google.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: > -----Original Message----- > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > Sent: Tuesday, April 4, 2017 1:39 PM > To: KY Srinivasan > 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 > Subject: Re: [PATCH 0/2] pci-hyperv: Some miscellaneous fixes >=20 > On Tue, Apr 04, 2017 at 07:54:33PM +0000, KY Srinivasan wrote: > > > -----Original Message----- > > > From: Bjorn Helgaas [mailto:helgaas@kernel.org] > > > Sent: Tuesday, April 4, 2017 12:04 PM > > > To: KY Srinivasan > > > 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 > > > 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 > > > > > > > > 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 >=3D 32 CPU= s > > > PCI: hv: Allocate interrupt descriptors with GFP_ATOMIC > > > > > Thank you. > > > > > There were two copies of [1/2], which makes this error-prone. I appl= ied > > > 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 the= m > for > > > v4.11. If you want them in v4.11, please supply those additional det= ails. > > > > 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. >=20 > No need to resend, but I do need more details about what issues these fix > and why they're more urgent than garden-variety bug fixes that are planne= d > for v4.12. In general for-linus is for fixing problems we added during t= he > merge window, or other high-priority, low-risk changes. For sure I want to get this into 4.12. Since it fixes issues that have been= there for a long time, (including 4.11), it would be good to get it into 4.11 as well.=20 Regards, K. Y >=20 > Bjorn