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

[Xen-devel] Physical memory layout for dom0?


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: Jiang Wang <jwangzju@xxxxxxxxx>
  • Date: Tue, 23 Jun 2009 11:30:29 -0400
  • Delivery-date: Tue, 23 Jun 2009 08:31:03 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Ca5F09Lg4b2Xc1ZKNhycVLgvfXSVHyf0LP6nEZGlx7e8PqXyMmUGt7lk+7L0AM2U18 fmUBgz5LVeCE61/u63lH/Ll4TnikHwuFt/78oioA/DSeK2wmR+UMFGt/eyBz9FnfjMBU hZWCUUm2Xao6u1vSJg4ZrOiCq2ncob5AOF8jY=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi:

I want to understand the physical memory (or machine memory) layout
for dom 0 (suppose Linux is dom 0). In a normal Linux for x86-32, the
Linux kernel is linear mapped, and the physical address of a function
or variable is  (va - 0xc0000000). I can find out the physical address
given the virtual address of a function. In Xen, the memory of
hypervisor is also linear mapped and I can find it in
http://lxr.xensource.com/lxr/source/xen/include/asm-x86/config.h. But
how about dom 0? Is its kernel memory also linear mapped to the
machine memory? How can I find out the physical (machine) address of a
variable of function given its virtual address in dom 0? I guess the
memory  of domU is dynamically mapped because it may be migrated to
another machine. But dom 0 should be linear mapped, right?

PS: I am working on Xen 3.3.1 with a linux 2.6.18-xen as dom 0.

Regards,

Jiang

_______________________________________________
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®.