[Xen-devel] Limitation in HVM physmap

[Wei Liu <wei.liu2@xxxxxxxxxx>]

Hi Jan, Tim and Keir

I currently run into the limitation of HVM's physmap: one MFN can only
be mapped into one guest physical frame. Why is it designed like that?

The scenario is that: when QEMU boots with OVMF (UEFI firmware), OVMF
will first map the framebuffer to 0x80000000, resulting the framebuffer
MFNs added to corresponding slots in physmap. A few moments later when
Linux kernel loads, it tries to map framebuffer MFNs to 0xf00000000,
which fails because those MFNs have already been mapped in other
locations. Is there a way to fix this?

Thanks
Wei

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