From: Christoph Hellwig <hch@infradead.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Piotr Jaroszynski <pjaroszynski@nvidia.com>,
Christoph Hellwig <hch@infradead.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
KY Srinivasan <kys@microsoft.com>,
Stephen Hemminger <sthemmin@microsoft.com>,
"olaf@aepfle.de" <olaf@aepfle.de>,
"vkuznets@redhat.com" <vkuznets@redhat.com>,
"driverdev-devel@linuxdriverproject.org"
<driverdev-devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain
Date: Tue, 25 Apr 2017 06:14:32 -0700 [thread overview]
Message-ID: <20170425131432.GA4714@infradead.org> (raw)
In-Reply-To: <8ff72ec3-d61e-07d9-8c9d-92951195b67d@nvidia.com>
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.
next prev parent reply other threads:[~2017-04-25 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 16:35 [PATCH] pci-hyperv: Use only 16 bit integer for PCI domain Haiyang Zhang
2017-04-20 18:33 ` Bjorn Helgaas
2017-04-20 18:37 ` Haiyang Zhang
2017-04-20 19:12 ` Christoph Hellwig
2017-04-24 23:06 ` John Hubbard
2017-04-25 13:00 ` Dan Carpenter
2017-04-25 13:14 ` Christoph Hellwig [this message]
2017-04-25 18:19 ` John Hubbard
-- strict thread matches above, loose matches on Subject: below --
2017-05-24 20:39 Haiyang Zhang
2017-05-24 20:43 ` Haiyang Zhang
[not found] ` <20170525141955.6cee8fbb@alans-desktop>
2017-05-25 15:52 ` Stephen Hemminger
2017-05-25 7:56 ` Christoph Hellwig
2017-06-19 21:07 ` Bjorn Helgaas
2017-06-19 21:10 ` Christoph Hellwig
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=20170425131432.GA4714@infradead.org \
--to=hch@infradead.org \
--cc=bhelgaas@google.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=haiyangz@microsoft.com \
--cc=jhubbard@nvidia.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=olaf@aepfle.de \
--cc=pjaroszynski@nvidia.com \
--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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).