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: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, <anthony.perard@xxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] libxl: Specify the target ram size to Qemu (new) when calling it
From: Keir Fraser <keir@xxxxxxx>
Date: Thu, 06 Jan 2011 14:35:04 +0000
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 06 Jan 2011 06:35:41 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:user-agent:date :subject:from:to:cc:message-id:thread-topic:thread-index:in-reply-to :mime-version:content-type:content-transfer-encoding; bh=1ANhoMM+bb27EqhwWM21/a1qHesJgIaZit9taXzhXws=; b=oaYukiq054AhUZkmoeqhpin+8B16pzF2b1AHziFYYgNzEHZQJRPvGFIaD9TYSkekNi vaeP8UPXtY/9xPcvTjGmvhdEB2Ua0w6GhPhhBFfKrYR/fki9sZmCX9GOqbhAUqxk48um JO+xn6yiWW1zk8cN9gHKyEQJxmQvoTW9rzzKU=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=Lib8aZGxyg2bfY00b6GnKQKIFMaeEgwjg3c2ibBQBJS0J+4UwR1lcCqs8FvIO+zEQZ vQUimwbsonQpeEEVx0uprXLmEeL5XQ3QGJRM1bsU27dI7/CbcaC0LO1I/isowQxMcx/L aafqoojcu4mdNRsBXHaDH3nkR265pRhQx5x0A=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19749.53621.856800.183479@xxxxxxxxxxxxxxxxxxxxxxxx>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcutrugY4Ul6MWKxOUCsMkrf/uXXpQ==
Thread-topic: [Xen-devel] [PATCH] libxl: Specify the target ram size to Qemu (new) when calling it
User-agent: Microsoft-Entourage/12.28.0.101117
On 06/01/2011 14:28, "Ian Jackson" <Ian.Jackson@xxxxxxxxxxxxx> wrote:

> anthony.perard@xxxxxxxxxx writes ("[Xen-devel] [PATCH] libxl: Specify the
> target ram size to Qemu (new) when calling it"):
>> This patch adds target_ram in device_model_info structure, to be used in
>> libxl_build_device_model_args_new. Qemu upstream needs to know about it.
> 
> I have applied this patch, thanks.
> 
> I'm just a little concerned, though: can you explain _why_ qemu
> upstream needs to know the target ram size ?

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.

 -- Keir

> Ian.
> 
> _______________________________________________
> 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