From: Sasha Levin <sashal@kernel.org>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: "bhelgaas@google.com" <bhelgaas@google.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"linux-hyperv@vger.kernel.org" <linux-hyperv@vger.kernel.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 <vkuznets@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision
Date: Mon, 5 Aug 2019 14:36:57 -0400 [thread overview]
Message-ID: <20190805183657.GD17747@sasha-vm> (raw)
In-Reply-To: <1564771954-9181-1-git-send-email-haiyangz@microsoft.com>
On Fri, Aug 02, 2019 at 06:52:56PM +0000, Haiyang Zhang wrote:
>Due to Azure host agent settings, the device instance ID's bytes 8 and 9
>are no longer unique. This causes some of the PCI devices not showing up
>in VMs with multiple passthrough devices, such as GPUs. So, as recommended
>by Azure host team, we now use the bytes 4 and 5 which usually provide
>unique numbers.
>
>In the rare cases of collision, we will detect and find another number
>that is not in use.
>Thanks to Michael Kelley <mikelley@microsoft.com> for proposing this idea.
>
>Signed-off-by: Haiyang Zhang <haiyangz@microsoft.com>
Acked-by: Sasha Levin <sashal@kernel.org>
Bjorn, will you take it through the PCI tree or do you want me to take
it through hyper-v?
--
Thanks,
Sasha
next prev parent reply other threads:[~2019-08-05 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 18:52 [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision Haiyang Zhang
2019-08-05 18:36 ` Sasha Levin [this message]
2019-08-06 18:55 ` Bjorn Helgaas
2019-08-06 18:55 ` Bjorn Helgaas
2019-08-06 19:45 ` Haiyang Zhang
-- strict thread matches above, loose matches on Subject: below --
2019-06-01 18:42 Sasha Levin
2019-05-19 22:28 Haiyang Zhang
2019-05-22 3:14 ` Dexuan Cui
[not found] ` <BYAPR21MB131778CC3A356745BC74EE3DCC000@BYAPR21MB1317.namprd21.prod.outlook.com>
2019-05-22 5:14 ` Dexuan Cui
2019-05-24 22:15 ` Sasha Levin
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=20190805183657.GD17747@sasha-vm \
--to=sashal@kernel.org \
--cc=bhelgaas@google.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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: link
Be 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.