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

[Xen-devel] Dom0 Virtual Memory

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Eric Benton" <benton71@xxxxxxxxx>
  • Date: Mon, 23 Oct 2006 12:42:12 +0200
  • Delivery-date: Mon, 23 Oct 2006 03:42:31 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=R5IuFahhnPNOLey1svKrL+ERMQu7KwyE00/OKybZK/pHacNDoELwvA4O9jOqP6Iq9H24c9+vD1jAmHO1dSxK0ioEsszGa7arcevWyfdmQvMMHxEdoqR/eurGf0wavkFe0eHqMtabyG97w8CCSQQMWw4ZPRt/1JlSvAemY2L9YjU=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


I looked at the sources and figured out all about the P2M, M2P tables and mappings,
Now I'm trying to figure out how dom0 virtual memory is implemented, and I have some questions.

The platform I'm working on is x86 with Intel VT enabled.

1. Is dom0 virtual memory managed differently than the other domains? what about hvms? and domUs?
2. What tables are used to manage the virtual memory?
3. What is the easiest method to do a dom0 virtual address to machine address translation (from Xen itself)?

Thanks for your help in advance!

Xen-devel mailing list



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