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

2019-08-13 Thread Haiyang Zhang
o...@aepfle.de; vkuznets ; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH v3] PCI: hv: Detect and fix Hyper-V PCI domain number > collision > > On Tue, Aug 13, 2019 at 12:55:59PM +, Haiyang Zhang wrote: > > > > > > > -Original Message- > > &g

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

2019-08-13 Thread Lorenzo Pieralisi
x- > > hyp...@vger.kernel.org; linux-...@vger.kernel.org; KY Srinivasan > > ; Stephen Hemminger ; > > o...@aepfle.de; vkuznets ; linux- > > ker...@vger.kernel.org > > Subject: Re: [PATCH v3] PCI: hv: Detect and fix Hyper-V PCI domain number > > collision > > > > On

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

2019-08-13 Thread Haiyang Zhang
o...@aepfle.de; vkuznets ; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH v3] PCI: hv: Detect and fix Hyper-V PCI domain number > collision > > On Mon, Aug 12, 2019 at 06:20:53PM +, Haiyang Zhang wrote: > > Currently in Azure cloud, for passthrough devices including GP

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

2019-08-13 Thread Lorenzo Pieralisi
On Mon, Aug 12, 2019 at 06:20:53PM +, Haiyang Zhang wrote: > Currently in Azure cloud, for passthrough devices including GPU, 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