Re: [Xen-devel] [edk2] [PATCH RFC 0/7] OvmfPkg: make OVMF fully working with Xen

[Jordan Justen <jljusten@xxxxxxxxx>]

On Sat, Nov 16, 2013 at 5:31 PM, Wei Liu <liuw@xxxxxxxxx> wrote:
> On Sat, Nov 16, 2013 at 3:31 AM, Jordan Justen <jljusten@xxxxxxxxx> wrote:
>> When I try to boot this on qemu or kvm, it asserts because the video
>> framebuffer address is NULL.
>
> That's expected because of the hack. ;-)

I see. But, I don't want to spend to much time considering it if is
not going to work with QEMU & KVM. :)

I think a simpler approach would be to retain the enumeration and
figure out a memory range that works with Xen.

>> On Fri, Nov 15, 2013 at 7:58 AM, Wei Liu <wei.liu2@xxxxxxxxxx> wrote:
>>> Wei Liu (7):
>>>   HACK: Use DeutPkg/PciRootBridgeNoEnumeration and
>>>     PciBusNoEnumerationDxe
>>
>> These modules would need to move to PcAtChipsetPkg in the non-hack version.
>>
>> Actually, it would be even better if the generic version of these
>> modules could be tweaked with a PCD to not do enumeration.

My first choice would be to add a PCD to MdeModulePkg/MdeModulePkg.dec
that prevents enumeration in
MdeModulePkg/Bus/Pci/PciBusDxe/PciBusDxe.inf, and continue to use this
main driver. But, I don't know how easy those changes would be to
make. It probably would also mean changing
PcAtChipsetPkg/PciHostBridgeDxe/PciHostBridgeDxe.inf by looking at the
same PCD. If some OVMF environments require enumeration, and some
don't then this would allow us to choose what will happen at runtime.

The only other option would be to move those modules to PcAtChipset.
But, first we'd have to prove that QEMU & KVM are okay with using
those drivers.

-Jordan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel