From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754207AbdDDTyh (ORCPT ); Tue, 4 Apr 2017 15:54:37 -0400 Received: from mail-sn1nam02on0130.outbound.protection.outlook.com ([104.47.36.130]:40983 "EHLO NAM02-SN1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753148AbdDDTyg (ORCPT ); Tue, 4 Apr 2017 15:54:36 -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: AQHSpMmKvQcA1nZCgEO6BA0G7ITUJKG1ormAgAAIAcA= Date: Tue, 4 Apr 2017 19:54:33 +0000 Message-ID: References: <1490378800-26907-1-git-send-email-kys@exchange.microsoft.com> <20170404190331.GD27692@bhelgaas-glaptop.roam.corp.google.com> In-Reply-To: <20170404190331.GD27692@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;SN1PR0301MB2111;7:+R4pj+WsX19i2vkhKgJ2aW4TB92NfG8wl49uFEnV8I275og28CzdvvApWZ7IWn3ycEyT1gqojj/z/ZVgB/vv20kIiH8iH2eLb1PKzW5y7aX5z/9m/6UhSkyuIzhPmlDhUUjLl5zSMOGoL8amSRnU/7lvcpVmVHUtTZexUEs+itmoDWRwvT38mXz/sO4ZPkx2GwxCllQCMYhgx4kfRK1Qmsx+9QU6iC3nHJMrowA3NGou4s2+DJtli+E4pU71JiJ9VqlLdrqy1fE/sM2+b6/zCl1HS/huI9nC/xeN+y5VhtikNpN6wFne5DPjuM+a7o3B7mRqwdMR9aO+YWYwxn951J2Ppzp9RgUtGX1Oxwh0+CQ= x-ms-office365-filtering-correlation-id: 767d8e0f-cd16-49a7-63f6-08d47b946a72 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);SRVR:SN1PR0301MB2111; 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)(10201501046)(3002001)(93006095)(93001095)(6055026)(61426038)(61427038)(6041248)(20161123564025)(20161123555025)(20161123560025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(6072148);SRVR:SN1PR0301MB2111;BCL:0;PCL:0;RULEID:;SRVR:SN1PR0301MB2111; x-forefront-prvs: 0267E514F9 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(39860400002)(39450400003)(39410400002)(39400400002)(39850400002)(39840400002)(377454003)(43784003)(13464003)(24454002)(3280700002)(3660700001)(2906002)(53936002)(9686003)(99286003)(54906002)(6116002)(102836003)(110136004)(6246003)(107886003)(10090500001)(38730400002)(6436002)(2900100001)(86362001)(189998001)(122556002)(77096006)(6506006)(55016002)(7696004)(2950100002)(229853002)(5660300001)(76176999)(8936002)(5005710100001)(10290500002)(8676002)(81166006)(53546009)(25786009)(33656002)(54356999)(50986999)(4326008)(74316002)(8990500004)(7736002)(305945005)(7416002)(6916009);DIR:OUT;SFP:1102;SCL:1;SRVR:SN1PR0301MB2111;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 19:54:33.5118 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR0301MB2111 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 v34JslsY003646 > -----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. Thanks, K. Y > > Bjorn From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 19:54:33 +0000 Message-ID: References: <1490378800-26907-1-git-send-email-kys@exchange.microsoft.com> <20170404190331.GD27692@bhelgaas-glaptop.roam.corp.google.com> In-Reply-To: <20170404190331.GD27692@bhelgaas-glaptop.roam.corp.google.com> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 List-ID: > -----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 >=20 > 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(-) >=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