Hi Christian? They are diffeent code except acpi timer is simliar my old
one, which was reject by you all the time:)
Thanks,
Winston,
Wang, Winston L wrote:
> Hi Christian, Ian and Kair,
>
> I think current hvm acpi support is broken.
> We noticed qemu to 0.82 with acpi support is introduced on changset
> 10957, it is conflict with xen hvm acpi code, in ../ioemu/hw/cp.c
> start from ln 860:
>
> cmos_init(ram_size, boot_device, bs_table, timeoffset);
>
> /* using PIIX4 acpi model */
> if (pci_enabled && acpi_enabled)
> pci_piix4_acpi_init(pci_bus, piix3_devfn + 3);
>
> if (pci_enabled && usb_enabled) {
> usb_uhci_init(pci_bus, piix3_devfn + 2);
> }
>
> if (pci_enabled && acpi_enabled && 0) {
> piix4_pm_init(pci_bus, piix3_devfn + 3);
> }
> ...
> /* XXX: should be done in the Bochs BIOS */
> if (pci_enabled) {
> pci_bios_init();
> if (acpi_enabled)
> acpi_bios_init();
> }
> }
>
> The above code generate two acpi tables and acpi pci piix func3
> device when acpi=1 in hvm guest platform.
>
> Two sets of acpi can not co-exist:) What acpi set do we need to keep?
> What is the advatage for that?
>
> We are cureent have to use changset 10955 puls acpi_init_fix.patch
> for acpi related development.
>
> Regards,
>
> Winston,
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|