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] libxl: Specify the target ram size to Qemu (new)

To: Anthony Perard <anthony.perard@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] libxl: Specify the target ram size to Qemu (new) when calling it
From: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Date: Thu, 6 Jan 2011 15:46:03 +0000
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>
Delivery-date: Thu, 06 Jan 2011 07:47:09 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.1.10.1101061452330.4415@xxxxxxxxxxxxxxxxxxxxxxx>
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: <C94B8398.1132B%keir@xxxxxxx> <alpine.DEB.1.10.1101061452330.4415@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Anthony Perard writes ("Re: [Xen-devel] [PATCH] libxl: Specify the target ram 
size to Qemu (new) when calling it"):
> On Thu, 6 Jan 2011, Keir Fraser wrote:
> > Qemu used to be responsible for initialising BIOS info tables, including
> > memory size information such as e820, in lieu of the virtual BIOS doing it.
> > I ripped all that out from our diverged tree, and put it in
> > hvmloader/rombios, but maybe they still do it in upstream qemu. I think it
> > would be harmless if so, since hvmloader/rombios will overwrite/ignore.
> 
> There are another reason, qemu "allocate" the memory for the vga at a
> dynamic address. In qemu-xen, this address is static. So qemu need to
> know the size of the ram to put the memory of the vga after the ram.
> Qemu do the same for other memory like the rom of a nic.
> 
> Information about the ram is put in the struct RAMBlock of qemu.

Right.  OK, I'll stop worrying :-).

Ian.

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

<Prev in Thread] Current Thread [Next in Thread>