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

[Xen-devel] about map_pages_to_xen call during boot memory allocator initialization


  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "余上" <yusunn@xxxxxxxxx>
  • Date: Sat, 16 Feb 2008 19:31:44 +0800
  • Delivery-date: Sat, 16 Feb 2008 03:32:08 -0800
  • 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=OC5fq5CwN51DisO3VtU9C6eWJ40B1UI85bD3Dh/lkdQV1RE9F8j+T5QdDhoC0pfHV6oj2pfdrdwPqnlF8npNp+Yrc7YdpSScprJtxi2kOXeUQ7CNubNFzi/wT3VkQL2QXeA7y+fOwt3sJsJTO88RWzywnVW/LTNQFmDwZCtwWJA=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hi All,
I know that during the initialization of boot memory allocator ,
memory is mapped into Xen's pagetable and I know this is a 1:1 mapping
under x86_32 which means the physical address equals the linear
address . So what purpose is this mapping? After all , boot allocator
just return page frame number , not the physical address the caller
must do another mapping , for example , in init_frametable .

Thank you very much
yushang

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