[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] X86_64 and 4GB RAM using Flat Memory Model?
- To: John Hannfield <hal9020@xxxxxxxxx>
- From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
- Date: Sat, 28 Apr 2007 15:35:41 +0100
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Sat, 28 Apr 2007 07:32:40 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AceJon7lvVSwAvWVEduvMgAWy6hiGQ==
- Thread-topic: [Xen-devel] X86_64 and 4GB RAM using Flat Memory Model?
On 28/4/07 15:30, "John Hannfield" <hal9020@xxxxxxxxx> wrote:
>> What does the start of a native Linux dmesg output look like (i.e, the bits
>> where it prints out the memory map)?
> Yes, it's quite different.
> Now that you mention it, xen sees the memory which are marked as (usable),
> but not the ones marked as (reserved). Whereas debian etch kernel sees
> the (reserved) ones as well. Below if the dmesg output from the debian etch
Which bootloader are you using to boot Xen? It's the bootloader which
provides the memory map.
Xen-devel mailing list