From: Tim Deegan <tim@xen.org>
To: Mj Embd <mj.embd@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: [Query] Xen nomenclature mapping to ARMv7
Date: Fri, 4 Oct 2013 14:04:19 +0100 [thread overview]
Message-ID: <20131004130419.GA68338@ocelot.phlegethon.org> (raw)
In-Reply-To: <CAPUj1ONDLhjK3V0Jh-+h84ELYuK9FOD-y57Vtpdu3yaSz1Pjyg@mail.gmail.com>
At 18:16 +0530 on 04 Oct (1380910571), Mj Embd wrote:
> Hi,
>
> I was debugging a problem and got confused into gmfn, gpfn, mfn.
>
> There are 4 addresses when running a VM on arm
> (a) Guest Virtual
> (b) Guest Physical
> (c) IPA
> (d) Real Physical.
>
> MFN is AFAIK is (d). Not able to map gmfn and gpn to (a)(b)(c).
On ARM, MFN is (d); GFN is (c) (== (b) too, I think).
GMFN and GPFN are older terms that aren't consistently used, and we
really ought to get rid of them. Please don't use them in new code.
On ARM they'll also mean (c).
Tim.
prev parent reply other threads:[~2013-10-04 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-04 12:46 [Query] Xen nomenclature mapping to ARMv7 Mj Embd
2013-10-04 12:53 ` Ian Campbell
2013-10-04 13:04 ` Tim Deegan [this message]
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=20131004130419.GA68338@ocelot.phlegethon.org \
--to=tim@xen.org \
--cc=mj.embd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).