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
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
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
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
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 bytes 8 and 9 provided by the host are no longer unique. This can
cause
5 matches
Mail list logo