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] [HVM] [RFC] Moving the e820 table creation into

To: Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] [HVM] [RFC] Moving the e820 table creation into hvmloader
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Wed, 8 Nov 2006 10:06:10 -0500
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 08 Nov 2006 07:06:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C1779D14.42B5%keir@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

Keir Fraser <keir@xxxxxxxxxxxxx> wrote on 11/08/2006 09:41:24 AM:

> On 8/11/06 14:17, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> > We can just make the ACPI range statically a page bigger. It's no big loss
> > (consider that we squander >100kB of memory between 0xC0000 and 0xF0000
> > right now), and at some point in the near future we'll get rid of the acpi
> > option and always produce ACPI tables. There are just a few interrupt issues
> > to sort out first.
>
> So I suppose you are not going to take the patch.

> Correct. A bunch of complexity there for negligible benefit that I can see.

In that case libxc should #include the acpi2_0.h and get its ACPI_PHYSICAL_BASE & ACPI_TABLE_SIZE parameters from there.

>
> >
> > The printk patch could be useful, however, since hvmloader is going to get
> > more complicated in other ways and we'll want to get tracing out of it.
>
> Which printk patch? Are you going to disable debugging there altogther?

>
> The printk stuff that is in the patch you sent, which you took from vmxassist.


I will let you apply that part then.


  Stefan
>
>  -- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>