WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH V3 0/6] firmware changes as part of QEMU/Xen merg

To: anthony.perard@xxxxxxxxxx
Subject: Re: [Xen-devel] [PATCH V3 0/6] firmware changes as part of QEMU/Xen merge.
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Fri, 29 Oct 2010 16:11:10 +0300
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 29 Oct 2010 06:11:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1288354119-1916-1-git-send-email-anthony.perard@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1288354119-1916-1-git-send-email-anthony.perard@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Oct 29, 2010 at 01:08:33PM +0100, anthony.perard@xxxxxxxxxx wrote:
> From: Anthony PERARD <anthony.perard@xxxxxxxxxx>
> 
> This patches are for Xen-unstable and Qemu-DM.
> 
> With the integration of Xen into QEMU, we would like to minimise the change
> and use the ACPI implementation of QEMU. So there are some change to make on
> the firmware to match the QEMU's BIOS. Some IO Ports are different and the
> sleep state values are different.
> 
> Change with the v2->v3:
> 
> Xen will register the old ioport by default and switch to the new ioport if 
> the
> HVM_PARAM_ACPI_NEW_IOPORT is set. So, this series come with a new function,
> unregister_io_handler, and a new HVM_PARAM.
> 

Should it be called something else than HVM_PARAM_ACPI_NEW_IOPORT ?
After a couple of years "NEW" might not make much sense anymore..

IOPORT_V2 ? Or something..

-- Pasi

> 
> Change v1->v2:
> 
> This time, both old and new ioport are handled.
> In QEMU-Xen, the choice between one or the other is made when a saved state is
> restored.
> In Xen, both ioports are registered.
> 
> 
> Anthony PERARD (5):
>   firmware, Change ACPI IO addresses and values to match QEMU BIOS.
>   xen, Introduce unregister_io_handler
>   xen, Intruduce pmtimer_change_ioport and HVM_PARAM_ACPI_NEW_IOPORT.
>   firmware, Set HVM_PARAM_ACPI_NEW_IOPORT
>   libxc, save/restore, Save the HVM_PARAM_ACPI_NEW_IOPORT
> 
>  tools/firmware/hvmloader/acpi/dsdt.asl |   12 ++++++------
>  tools/firmware/hvmloader/hvmloader.c   |   11 +++++++++++
>  tools/libxc/xc_domain_restore.c        |   12 ++++++++++++
>  tools/libxc/xc_domain_save.c           |   11 +++++++++++
>  tools/libxc/xg_save_restore.h          |    1 +
>  xen/arch/x86/hvm/hvm.c                 |    9 +++++++++
>  xen/arch/x86/hvm/intercept.c           |   26 ++++++++++++++++++++++++++
>  xen/arch/x86/hvm/pmtimer.c             |   26 ++++++++++++++++++++++++--
>  xen/include/asm-x86/hvm/io.h           |    8 ++++++++
>  xen/include/asm-x86/hvm/vpt.h          |    1 +
>  xen/include/public/hvm/ioreq.h         |   16 +++++++++++++---
>  xen/include/public/hvm/params.h        |    5 ++++-
>  12 files changed, 126 insertions(+), 12 deletions(-)
> 
> 
> QEMU-Xen change:
> 
> Anthony PERARD (1):
>   piix4acpi: change in ACPI to match the change in the BIOS.
> 
>  hw/piix4acpi.c |   99 ++++++++++++++++++++++++++++++++++++++++++++++---------
>  1 files changed, 82 insertions(+), 17 deletions(-)
> 
> -- 
> Anthony PERARD
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel