Re: [PATCH v6,1/2] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-20 Thread Lorenzo Pieralisi
On Thu, Aug 15, 2019 at 05:01:37PM +, Haiyang Zhang wrote: > Currently in Azure cloud, for passthrough devices, the host sets the device > instance ID's bytes 8 - 15 to a value derived from the host HWID, which is > the same on all devices in a VM. So, the device instance ID's bytes 8 and 9 > p

RE: [PATCH v6,1/2] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-16 Thread Haiyang Zhang
fle.de; vkuznets ; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH v6,1/2] PCI: hv: Detect and fix Hyper-V PCI domain > number collision > > On Thu, Aug 15, 2019 at 05:01:37PM +, Haiyang Zhang wrote: > > Currently in Azure cloud, for passthrough devices, the host sets

Re: [PATCH v6,1/2] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-16 Thread Lorenzo Pieralisi
On Thu, Aug 15, 2019 at 05:01:37PM +, Haiyang Zhang wrote: > Currently in Azure cloud, for passthrough devices, the host sets the device > instance ID's bytes 8 - 15 to a value derived from the host HWID, which is > the same on all devices in a VM. So, the device instance ID's bytes 8 and 9 > p

[PATCH v6,1/2] PCI: hv: Detect and fix Hyper-V PCI domain number collision

2019-08-15 Thread Haiyang Zhang
Currently in Azure cloud, for passthrough devices, the host sets the device instance ID's bytes 8 - 15 to a value derived from the host HWID, which is the same on all devices in a VM. So, the device instance ID's bytes 8 and 9 provided by the host are no longer unique. This affects all Azure hosts