[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] arch_init_memory() change

To: "Altobelli, David" <david.altobelli@xxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 24 Jun 2007 23:08:07 +0100
Delivery-date: Sun, 24 Jun 2007 15:06:06 -0700
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thread-index: Ace06mbWQQp4xXv+Rxe5UnP7edz9UQAv2u6cAAEfl9gALisa0AARSdk+
Thread-topic: [Xen-devel] arch_init_memory() change

On 24/6/07 15:00, "Altobelli, David" <david.altobelli@xxxxxx> wrote:

> I noticed this in version 3.0.3-rc5-8.el5, which does not have the code
> you mention in setup.c.  Sorry for not fully checking a newer version.
> 
> By the way, do you want to be sharing the ACPI region?  The choice
> currently seems to depend on how RAM regions are laid out - if there is
> a RAM region post-ACPI, then you will share it, otherwise not.

Everything that isn't in a page-aligned and -sized e820 ram region should be
marked as belonging to dom_io.

 -- Keir



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

References:
- RE: [Xen-devel] arch_init_memory() change
  - From: Altobelli, David

Prev by Date: Re: [Xen-devel] [PATCH] x86-64: clear DF for kernel when forwarding syscall
Next by Date: Re: [Xen-devel] It seems the "machine check exception handling" breaks HVM guest
Previous by thread: RE: [Xen-devel] arch_init_memory() change
Next by thread: [Xen-devel] gdbserver-xen frustration on x86_64
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.