From: Keir Fraser <keir.xen@gmail.com>
To: Sengul Thomas <thomas.sengul@gmail.com>,
Xen Devel <xen-devel@lists.xen.org>
Subject: Re: Distinguishing gpfn, gmfn, mfn, and pfn
Date: Wed, 29 May 2013 08:27:31 +0100 [thread overview]
Message-ID: <CDCB6C73.53C60%keir.xen@gmail.com> (raw)
In-Reply-To: <CAJWjLtriXup0GCPuY5sW0nHK1bum29Lde0POUP9SeevTvJo8tA@mail.gmail.com>
On 29/05/2013 02:03, "Sengul Thomas" <thomas.sengul@gmail.com> wrote:
> Hi xen developers,
>
> I'm confused about the actual usage of the four types of frames.
> I can find the definition in xen/include/xen/mm.h, but would like
> to check my understanding is correct:
>
> 1) Is 2-stage MMU-supported (e.g., ARMv7 VE) translation
> auto-translated mode? Then, gpfn == gmfn.
>
> 2) Is gmfn --> mfn mapping the p2m table?
>
> 3) Paravirtualized x86 guest will have gpfn != gmfn, and it is
> quite hard to imagine. Could you tell me the difference
> between gpfn and gmfn? (for instance, when it is used)
There are basically two modes:
gmfn==gpfn: Guest does not see real machine physical addresses. p2m is done
by the hypervisor. This is like x86 HVM guests.
gmfn==mfn: Guest does see real machine physical addresses. Typically the
guest will have its own concept of a flat pseudophysical address space that
it maps to real machine addresses with its own p2m table. This is like x86
pure PV guests.
ARM7 VE does indeed support HVM for ARM, and gmfn==gpfn.
-- Keir
>
> thanks always,
> Thomas
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-05-29 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 1:03 Distinguishing gpfn, gmfn, mfn, and pfn Sengul Thomas
2013-05-29 7:27 ` Keir Fraser [this message]
2013-05-29 10:09 ` George Dunlap
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=CDCB6C73.53C60%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=thomas.sengul@gmail.com \
--cc=xen-devel@lists.xen.org \
/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.