[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] query on physical memory map for Xen?


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "pradeep singh rautela" <rautelap@xxxxxxxxx>
  • Date: Fri, 11 Apr 2008 11:44:26 +0530
  • Delivery-date: Thu, 10 Apr 2008 23:14:49 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=dP2Y2g1F2h3jyZCFMEjvQloALrRPQn0JExnFLZ70A6H4ckLwpFZM2b7vkqm+PhUyqRIcCcj6fskHH+Z1mUN1+ru2BXBVwKuRbvGE33hEgxIsxWzrg+rPkmIOfIUXXPB1222FTbQ8Giu3y/wkLOaVKoDqetl89K7YFmQvdbaKz4w=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi All,

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?

Any help will be appreciated.

Thanks,
-- 
Pradeep Singh Rautela
http://eagain.wordpress.com
http://emptydomain.googlepages.com

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.