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] query on physical memory map for Xen?

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] query on physical memory map for Xen?
From: "Peter Teoh" <htmldeveloper@xxxxxxxxx>
Date: Mon, 14 Apr 2008 13:43:46 +0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 13 Apr 2008 22:44:11 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=YtkPG5ljS8MdkRjFxVHOa5MPqgXUMLjr6OZUag0hxAs=; b=QieaFCr13PnuWHl+CZVMA80JgBfe7xv3zmlC3Aha5weormcNFcJ8QWvF2lHZ0oeSiwLoTJFdkzNC7f66fx5ViOhjEN4fxhKDsGt8rWcU2Q7dE31QVBqtaPRjrhxWxFCl8+XbG9LukpyT1OM+Zm44cywG6FxMkHqDxhaAuvmnoTc=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=nUShPkiG9b4DBHvfM0rkMHkFVByD2SAzoLoAQgOTZu36FtW0f9+jMJ2wuaTc0NDlS3kT2roUDfqBjFbZANbKrAIT29r7J9B/cTPSOa9NuHVeYr3Sv9tn3IabrcbKkxTnHaCvSKvYQ8YXU33xwxcztcPp43bf3+w0vIQs01uYbs8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C424C9A5.16331%keir.fraser@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <6bc632150804102314g29c10bfay129b23a11d2877fe@xxxxxxxxxxxxxx> <C424C9A5.16331%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Just curious, can anyone give a hint on where this 16GB max physical
memory is defined?

Doing some random search by strings I found these:

#define MAXMEM           0x3fffffffffffUL
#define MAXMEM                  (__FIXADDR_TOP-__PAGE_OFFSET-__VMALLOC_RESERVE)
#define MAXMEM_PFN      PFN_DOWN(MAXMEM)
#define ACPI_MEM_LIST_MAX               6
#define NR_NODE_MEMBLKS (MAX_NUMNODES*2)
#define EFI_MAX_MEMORY_TYPE             14
#define  PCI_X_CMD_MAX_READ     0x000c  /* Max Memory Read Byte Count */
#define  PCI_X_STATUS_MAX_READ  0x00600000      /* Designed Max Memory
Read Count */
#define GEO_TYPE_MAX            (GEO_TYPE_MEM+1)
#define NR_NODE_MEMBLKS (MAX_NUMNODES*2)
    *max_mfn = xc_memory_op(xc_handle, XENMEM_maximum_ram_page, NULL);
#define EFI_MAX_MEMORY_TYPE             14
#define MAXMEM           0x3fffffffffffUL
 * KEXEC_SOURCE_MEMORY_LIMIT maximum page get_free_page can return.
#define MAXMEM                  (__FIXADDR_TOP-__PAGE_OFFSET-__VMALLOC_RESERVE)
#define MAXMEM_PFN      PFN_DOWN(MAXMEM)
 * KEXEC_SOURCE_MEMORY_LIMIT maximum page get_free_page can return.
#define ACPI_MEM_LIST_MAX               6
#define XENMEM_maximum_ram_page     2
#define XENMEM_maximum_reservation  4
#define XENMEM_maximum_gpfn         14
#define NR_NODE_MEMBLKS (MAX_NUMNODES*2)
#define EFI_MAX_MEMORY_TYPE             14
#define GEO_TYPE_MAX            (GEO_TYPE_MEM+1)
#define NR_NODE_MEMBLKS (MAX_NUMNODES*2)

Not sure which one maps to this 16GB thing?   Thanks for the sharing :-).

On Fri, Apr 11, 2008 at 2:54 PM, Keir Fraser <keir.fraser@xxxxxxxxxxxxx> wrote:
> On 11/4/08 07:14, "pradeep singh rautela" <rautelap@xxxxxxxxx> wrote:
>
>  > Based on my understanding of the Xen code, I have a small query for you 
> all.
>  >
>  > Xen hypervisor can access only a max of 16GB of physical memory
>  > directly on x86 architecture.
>  > Is this correct inference?
>  >
>  > So does Xen hypervisor cannot touch memory about 16G directly? Does it
>  > employ some kind of temporary mapping like linux kernel to access
>  > memory above 16G then?
>
>  32-bit Xen does not use memory above 16GB at all. 64-bit Xen can use any
>  amount of memory, and is able to keep a permanent mapping of all of it.
>
>   -- Keir
>
>
>
>
>
>  _______________________________________________
>  Xen-devel mailing list
>  Xen-devel@xxxxxxxxxxxxxxxxxxx
>  http://lists.xensource.com/xen-devel
>



-- 
Regards,
Peter Teoh

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