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] Re: [PATCH] SeaBIOS/Xen: Compute the low RAM memory size

To: Kevin O'Connor <kevin@xxxxxxxxxxxx>, Julian Pidancet <julian.pidancet@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] SeaBIOS/Xen: Compute the low RAM memory size in the BDA according to the e820
From: Keir Fraser <keir@xxxxxxx>
Date: Mon, 14 Nov 2011 13:23:41 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, seabios@xxxxxxxxxxx, ian.campbell@xxxxxxxxxx
Delivery-date: Mon, 14 Nov 2011 05:24:39 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; 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; bh=7awhqFtci8043s4QuVn6oEvfVk39BNFaG2DkJdzCPtw=; b=Ac8H4mva525rmW4hBQDzW9LqjA7g2PA3FgPw/W4kzuPTH0ZlDTQaUHYiDO5Kl0St3a hd8WvILiVoe/a0TLo3MG9PHSvhW8JVC2frF3L397Ikn9wTaHAdqbRhJmdDN5gKz7X4Xs Y8Y5GNlBJktdkJIohvq+zpwqu0XDoYiqNc8XI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAE687A1.24CDF%keir.xen@xxxxxxxxx>
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: Acyiqu9P8I6IreVxm0qt+lGyuae+igAJbDM4
Thread-topic: [Xen-devel] Re: [PATCH] SeaBIOS/Xen: Compute the low RAM memory size in the BDA according to the e820
User-agent: Microsoft-Entourage/12.31.0.110725
On 14/11/2011 08:53, "Keir Fraser" <keir.xen@xxxxxxxxx> wrote:

> On 14/11/2011 03:36, "Kevin O'Connor" <kevin@xxxxxxxxxxxx> wrote:
> 
>> On Xen, the PCI init code isn't used, so assuming this struct doesn't
>> need to live in real "ram", I think it could live just about anywhere
>> past the end of ram.  Even with pciinit.c, addresses over 0xfc00000
>> (with the exception of a few bytes for hpet, apic, ioapic, and bios
>> image) could be used.
> 
> I suggest we stick it at FC000000, and shift hvmloader's mem_alloc()
> starting address up by one page to FC001000. The acpi build code will have
> to manually mem_hole_populate_ram() that one page before writing to it. This
> can then be documented in hvmloader/config.h which contains a description
> of, and defines for, the system memory map. This is by far the easiest
> solution to this problem; manually crafting an SSDT is a right pain in the
> arse, whereas this is maybe a 5-line patch.

Like the attached patch (untested), which is a bit larger than anticipated,
but actually allows code to be net deleted. :-)

 -- Keir

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

Attachment: 00-relocate-acpi-info
Description: Binary data

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