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

[Xen-ia64-devel] Question to memory handling for domU


  • To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
  • Date: Thu, 10 Aug 2006 15:13:47 +0200
  • Delivery-date: Thu, 10 Aug 2006 06:14:07 -0700
  • Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=Vv3y9yyflvLGQvrnoS5PD26fu96Q8GYwG31AKkCO5BDqdsMTyKCEFdottQ3enZJbvILSDRULNietAFUybD04LyZREo0EhMhZiURxPv1spy0eycXFDSTvAG4mQdMn4ZDv;
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>

Hi,

while I was playing with my mini-os and the memory a short question comes up:
What memory info is relevant and where gets the domU kernel loaded within the 
(for domU) configured memory?
I have 128MB configured for domU.
start_info->nr_pages gives me 8192 pages -> 128MB.
The memory given by the efi (EfiConventionalMemory) is physically between
0x200000 and 0x7ff4000 -> ~2MB are absent.
Do I have to take this efi memory only, right? How is the absent memory used?

My kernel gets loaded to physically address 0x4000000.
That means the kernel text and data are nearly in middle of the memory.
May this be? If yes - I have to check the this and split the memory to 
separate the kernel?
Thanks.

Dietmar


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


 


Rackspace

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