Re: [edk2] [PATCH v2] OvmfPkg/PlatformBootManagerLib: Connect the Xen drivers before loading NvVars

2016-06-01 Thread Gary Lin
On Wed, Jun 01, 2016 at 11:12:17AM +0200, Laszlo Ersek wrote: > On 06/01/16 09:51, Gary Lin wrote: > > On Tue, May 31, 2016 at 12:21:45AM -0700, Jordan Justen wrote: > >> On 2016-05-30 20:19:42, Gary Lin wrote: > >>> When OVMF tried to load the file-based NvVars, > >> > >> Tangent: Will Xen ever

Re: [edk2] [PATCH v2] OvmfPkg/PlatformBootManagerLib: Connect the Xen drivers before loading NvVars

2016-06-01 Thread Laszlo Ersek
On 06/01/16 09:51, Gary Lin wrote: > On Tue, May 31, 2016 at 12:21:45AM -0700, Jordan Justen wrote: >> On 2016-05-30 20:19:42, Gary Lin wrote: >>> When OVMF tried to load the file-based NvVars, >> >> Tangent: Will Xen ever add a r/w flash emulation for variables like >> QEMU/KVM? >> >>> it checked

Re: [edk2] [PATCH v2] OvmfPkg/PlatformBootManagerLib: Connect the Xen drivers before loading NvVars

2016-05-31 Thread Jordan Justen
On 2016-05-30 20:19:42, Gary Lin wrote: > When OVMF tried to load the file-based NvVars, Tangent: Will Xen ever add a r/w flash emulation for variables like QEMU/KVM? > it checked all the PCI > instances and connected the drivers to the mass storage device. However, > Xen registered its PCI

[edk2] [PATCH v2] OvmfPkg/PlatformBootManagerLib: Connect the Xen drivers before loading NvVars

2016-05-30 Thread Gary Lin
When OVMF tried to load the file-based NvVars, it checked all the PCI instances and connected the drivers to the mass storage device. However, Xen registered its PCI device with a special class id (0xFF80), so ConnectRecursivelyIfPciMassStorage() couldn't recognize it and skipped the driver