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

[Xen-devel] question about the meaning of memory auto-translate and para

To: tgh <tianguanhua@xxxxxxxxxx>
Subject: [Xen-devel] question about the meaning of memory auto-translate and paravirtual and no pseudophysical overlay
From: tgh <tianguanhua@xxxxxxxxxx>
Date: Thu, 05 Apr 2007 10:19:08 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 04 Apr 2007 19:17:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4611C2F7.9060800@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: <991B62EB36934C4EBD5B605518A724764C421E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4611C2F7.9060800@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.7 (Windows/20060909)
hi
I try to understand the code of xen memory ,and I am confused about the memory-management modes,could someone help me

there are gmfn, gpfn and pfn in the xen ,and in the /xen/include/xen/mm.h there are some explanation about them as follows:

* 1. gpfn/gpaddr: A guest-specific pseudo-physical frame number or address.
* 2. gmfn/gmaddr: A machine address from the p.o.v. of a particular guest.
* 3. mfn/maddr:   A real machine frame number or address.
* 4. pfn/paddr:   Used in 'polymorphic' functions that work across all
*                 address spaces, depending on context. See the pagetable
*                 conversion macros in asm-x86/page.h for examples.
* Also 'paddr_t' is big enough to store any physical address.
*

I seems to understand the meaning about them,but I am confused about the different memory-management modes as follows

* This scheme provides consistent function and variable names even when
* different guests are running in different memory-management modes.
* 1. A guest running in auto-translated mode (e.g., shadow_mode_translate())
*    will have gpfn == gmfn and gmfn != mfn.
* 2. A paravirtualised x86 guest will have gpfn != gmfn and gmfn == mfn.
* 3. A paravirtualised guest with no pseudophysical overlay will have
*    gpfn == gpmfn == mfn.
*

what is the meaning about auto-translated mode,is it not the same with paravirtualised one ? does the auto-translated mode work for hvm and shadow mode? how does it work? and what is the mechanism about paravirtualised guest with no pseudophysical overlay?

I am confused about it

could you help me
Thanks in advance


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