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

[Xen-devel] Why the machine address is out of the end of real physical memory?


  • To: Xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "ken lost" <kenlost@xxxxxxxxx>
  • Date: Thu, 24 Apr 2008 09:20:57 +0800
  • Delivery-date: Wed, 23 Apr 2008 18:21:29 -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=TIHBAOKDTX8RotRDzo4NxbIzBHq7OfbwVMcBBsScAtv9DvklTv2SALZ0nR/GQJt0b7uDctKydmehSkAd/zWqOGZeQwMssNJ5pis3b9Ej0Y6n1HQFnDU6j8mWMnbVvS9ifQ8F0PwI0u03PkC5mPV2RuSi8Ho81l8eo67/HXUyoM8=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Hello evrybody,

I have a machine with 8G RAM, which runs on Redhat Enterprise linux
5.1(kernel 2.6.18-53.el5xen, i386 platform PAE, xen 3.0.3 ) .  My
driver need run on Domain0.
The code has this code for get a momory and its machine address for BIOS.

           dmamem_buff = (void*)__get_free_pages( GFP_KERNEL|GFP_DMA,
DMA_MEMORY_ORDER);
           maddr_t ma = virt_to_machine(dmamem_buff) ;
           printk("machine address is %lldM\n", ma/1024/1024 );
           printk("machine address is 0x%llx\n", ma );
...

But the result :
           machine address is 8487M
           machine address is 0x212790000

Why the machine address is out of the end of real physical memory?

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