On 5/26/2011 1:19 PM, Andriy Gapon wrote:
on 26/05/2011 22:25 Nate Lawson said the following:
This might be a useful source for making ACPI compatible with Windows.
http://dslab.epfl.ch/pubs/revnic
I had thought of a project like this before. My idea was to take QEMU
and map PCI config space and allow direct access to the bare hardware
for only one device. The developer would install Windows in this QEMU
image on a system with the target device, identify it by its PCI id, and
then run Windows normally. The VM would log the driver's accesses to
config space as well as use CoW semantics for DMA accesses to memory and
IO ports.
Something like this?
http://www.serialice.com/News/News.html
Now that Intel/AMD support hardware virtualization and DMA isolation, it
would be better to do this with a modified Xen hypervisor.
Yes, that is a nice project but requires flashing firmware. With
hardware virtualization you can trap all IO accesses and do this in
software.
--
Nate
___
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to freebsd-acpi-unsubscr...@freebsd.org
