RE: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-06 Thread Haiyang Zhang
o...@aepfle.de; vkuznets ; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number > collision > > On Fri, Aug 02, 2019 at 06:52:56PM +, Haiyang Zhang wrote: > > Due to Azure host agent settings, the device instance ID's b

Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-06 Thread Bjorn Helgaas
On Mon, Aug 05, 2019 at 02:36:57PM -0400, Sasha Levin wrote: > On Fri, Aug 02, 2019 at 06:52:56PM +, 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 mul

Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-06 Thread Bjorn Helgaas
On Fri, Aug 02, 2019 at 06:52:56PM +, 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 Azur

Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-05 Thread Sasha Levin
On Fri, Aug 02, 2019 at 06:52:56PM +, 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

[PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-02 Thread Haiyang Zhang
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

[PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-06-01 Thread Sasha Levin
From: Haiyang Zhang 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 u

Re: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-05-24 Thread Sasha Levin
On Sun, May 19, 2019 at 10:28:37PM +, 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

RE: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-05-21 Thread Dexuan Cui
> From: Stephen Hemminger > Sent: Tuesday, May 21, 2019 9:40 PM > > Thanks for working this out with the host team. > Now if we could just get some persistent slot information it would make udev > in systemd happy. The slot info comes from the serial number "hpdev->desc.ser", which may not gua

RE: [PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-05-21 Thread Dexuan Cui
> From: linux-hyperv-ow...@vger.kernel.org > Sent: Sunday, May 19, 2019 3:29 PM > > 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 r

[PATCH] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-05-19 Thread Haiyang Zhang
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