[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190806185531.GS151852@google.com>
Date: Tue, 6 Aug 2019 13:55:31 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Haiyang Zhang <haiyangz@...rosoft.com>,
"lorenzo.pieralisi@....com" <lorenzo.pieralisi@....com>,
"linux-hyperv@...r.kernel.org" <linux-hyperv@...r.kernel.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
KY Srinivasan <kys@...rosoft.com>,
Stephen Hemminger <sthemmin@...rosoft.com>,
"olaf@...fle.de" <olaf@...fle.de>, vkuznets <vkuznets@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number
collision
On Mon, Aug 05, 2019 at 02:36:57PM -0400, Sasha Levin wrote:
> 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@...rosoft.com> for proposing this idea.
> > Signed-off-by: Haiyang Zhang <haiyangz@...rosoft.com>
>
> Acked-by: Sasha Levin <sashal@...nel.org>
>
> Bjorn, will you take it through the PCI tree or do you want me to take
> it through hyper-v?
Lorenzo usually applies patches to drivers/pci/controller/*, so that
would be my preference.
Bjorn
Powered by blists - more mailing lists