On Mon, 2016-02-01 at 13:49 +0100, Gerd Hoffmann wrote:
> > > Maybe we should define the interface as "guest writes 0xfc to pick
> > > address, qemu takes care to place opregion there". That gives us the
> > > freedom to change the qemu implementation (either copy host opregion or
> > > map the
Hi,
> Thanks for the tip that seabios allocated pages automatically become
> e820 reserved, that simplifies things a bit.
It's common practice for all firmware. The e820 table from qemu is just
a starting point, it is not passed on to the guest os as-is. All
permanent allocations (acpi
Hi,
> +realloc:
> +opregion = malloc_high(size * 1024);
memalign_high(PAGE_SIZE, size * 1024);
> > I'd have qemu copy the data on 0xfc write then, so things continue to
> > work without updating seabios. So, the firmware has to allocate space,
> > reserve it etc., and programming the
On Fri, 2016-01-29 at 08:09 +0100, Gerd Hoffmann wrote:
> Hi,
>
> > 1) The OpRegion MemoryRegion is mapped into system_memory through
> > programming of the 0xFC config space register.
> > a) vfio-pci could pick an address to do this as it is realized.
> > b) SeaBIOS/OVMF could program this.
Hi,
> 1) The OpRegion MemoryRegion is mapped into system_memory through
> programming of the 0xFC config space register.
> a) vfio-pci could pick an address to do this as it is realized.
> b) SeaBIOS/OVMF could program this.
>
> Discussion: 1.a) Avoids any BIOS dependency, but vfio-pci would
On Tue, 2016-01-05 at 12:41 +0100, Gerd Hoffmann wrote:
> Hi,
>
> We have some code in our tree to support pci passthrough of intel
> graphics devices (igd) on xen, which requires some chipset tweaks
> for (a) the host bridge and (b) the lpc/isa-bridge to meat the
> expectations of the guest
