Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1947645AbdDYNOp (ORCPT ); Tue, 25 Apr 2017 09:14:45 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:38676 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1428897AbdDYNOf (ORCPT ); Tue, 25 Apr 2017 09:14:35 -0400 Date: Tue, 25 Apr 2017 06:14:32 -0700 From: Christoph Hellwig To: John Hubbard Cc: Haiyang Zhang , Bjorn Helgaas , Piotr Jaroszynski , Christoph Hellwig , "linux-pci@vger.kernel.org" , KY Srinivasan , Stephen Hemminger , "olaf@aepfle.de" , "vkuznets@redhat.com" , "driverdev-devel@linuxdriverproject.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain Message-ID: <20170425131432.GA4714@infradead.org> References: <1492706123-22913-1-git-send-email-haiyangz@exchange.microsoft.com> <8ff72ec3-d61e-07d9-8c9d-92951195b67d@nvidia.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8ff72ec3-d61e-07d9-8c9d-92951195b67d@nvidia.com> User-Agent: Mutt/1.8.0 (2017-02-23) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 868 Lines: 21 Hi John, please fix your quoting of the previous mails, thanks! What ACPI defines does not matter at all. Linux uses 32-bit domains IDs, and on x86 specifily uses those for non-ACPI enumarated domains (e.g. VMD). You've also not demontrated any issue with any Linux driver yet. > Also...it would be nice if we could use Haiyang's patch as at least a > temporary fix, because distros are just today releasing the previous code, > and HyperV will start breaking "occasionally", depending on whether the > 32-bit virtual (fake) PCI domain fits within 16 bits. (If not, then we can > rush out a driver update to fix it, but there will be a window of time with > some breakage there.) Just send the fix to whatever driver is broken to the driver maintainer. But I can't find a single broken driver in the tree, and as you know nothing else matters for Linux anyway.