From: tgh <tianguanhua@ncic.ac.cn>
To: tgh <tianguanhua@ncic.ac.cn>
Cc: xen-devel@lists.xensource.com
Subject: question about the meaning of memory auto-translate and paravirtual and no pseudophysical overlay
Date: Thu, 05 Apr 2007 10:19:08 +0800 [thread overview]
Message-ID: <46145C9C.7060009@ncic.ac.cn> (raw)
In-Reply-To: <4611C2F7.9060800@ncic.ac.cn>
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
next prev parent reply other threads:[~2007-04-05 2:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 3:27 About IO Liu, Huahang
2007-03-30 3:36 ` Li, Xin B
2007-04-03 1:57 ` Liu, Huahang
2007-04-03 6:29 ` Keir Fraser
2007-03-30 8:01 ` Guy Zana
2007-04-03 2:59 ` question about memory auto-translate and paravirtual and no pseudophysical overlay tgh
2007-04-05 2:19 ` tgh [this message]
2007-04-07 16:23 ` question about the meaning of " Mark Williamson
2007-04-09 12:59 ` tgh
2007-04-11 21:28 ` Mark Williamson
2007-04-12 0:50 ` tgh
2007-04-12 15:37 ` Mark Williamson
2007-04-13 0:34 ` tgh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46145C9C.7060009@ncic.ac.cn \
--to=tianguanhua@ncic.ac.cn \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.