WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] question about machine-to-physic table and phy-to-machin

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] question about machine-to-physic table and phy-to-machine table
From: Mark Williamson <mark.williamson@xxxxxxxxxxxx>
Date: Tue, 27 Mar 2007 05:14:53 +0100
Cc: Daniel Stodden <stodden@xxxxxxxxxx>, tgh <tianguanhua@xxxxxxxxxx>
Delivery-date: Mon, 26 Mar 2007 21:14:43 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <460333B8.70307@xxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <45F93B96.76E4.0078.0@xxxxxxxxxx> <460333B8.70307@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
>  I read the code ,there are machine-to-physic table and
> physic-to-machine table
> there are machine address for hardward address ,physic address for
> guestos's view hardware and virtual address ,is it right?
>
> phy-to-machine table is a mapping for guestos's view hardware to real
> hardward ,is it right?
> I am confused about the meaning and function of  machine-to-physic address

* Machine addresses represent real RAM in the host.  The memory a guest owns 
will certainly not start at 0 and will not necessarily be contiguous - it 
might be in a number of chunks with big gaps between.

* (pseudo)physical addresses represent the memory the guest owns.  This 
address space starts at 0 and is contiguous.

* Virtual addresses are used by software running in the guest, and by the 
guest kernel.  They're translated by the host CPU into machine addresses so 
that it can access the correct RAM.

Guests use physical addresses as an abstraction: most operating system memory 
management code assumes that the RAM owned by the OS starts at 0 and is 
contiguous.  Because this is not the case for Machine addresses under Xen, 
most of the guest's code is "tricked" by giving it pseudophysical addresses 
that look like it expects memory to look.

The P2M and M2P tables record the relationship between pseudophysical page 
frames (which the core OS code uses) and machine page frames (which the host 
really uses).  The Xen "architecture" code within the guest OS uses these 
tables to manage the translation between pseudophysical and machine page 
frames so that the guest's page tables can be handled correctly.  For 
paravirtualised guests, page tables must contain machine addresses - these 
must be translated from the pseudophysical addresses used by core OS code.

Hope that helps clarify how this all fits together, tgh.

Cheers,
Mark

-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel