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

[Xen-devel] domU's pseudo physical address mapping


  • To: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: "D.W. Luo" <danwei.luo@xxxxxxx>
  • Date: Tue, 3 Jan 2017 08:48:49 +0000
  • Accept-language: zh-CN, en-US
  • Delivery-date: Tue, 03 Jan 2017 08:51:28 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99
  • Thread-index: AdJll95sgxHeACyATW2HgkjYff2jWw==
  • Thread-topic: [Xen-devel] domU's pseudo physical address mapping

Hi All,

 

This is my first mail to this mail list, and nice to meet all of you!

 

Right now I’m porting XEN 4.8 to an ARMv8 board and I had met some problems

with domU’s pseudo physical address mapping.

 

Here is my situation:

I have a display control hardware that can move data from framebuffer to a display,

and I used passthrough method let domU use this hardware. The framebuffer lies in

domU’s RAM, and will be allocated a pseudo physical address during the boot process.

This address will also be past to my display control hardware.

But the problem is that this hardware will directly access this address to move data,

which means the framebuffer’s pseudo physical address must be 1:1 mapped

to actual physical address. But from my understanding, domU’s RAM is automatically

mapped to actual physical address by XEN.

 

So my question is:

Is there some way that I can set domU’s RAM to have a 1:1 mapping to actual physical

address so that pseudo physical address is the same as actual physical addresss?

 

Thanks in advance!

 

Best regards,

Danwei

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

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