From: valerij zaporogeci <vlrzprgts@gmail.com>
To: edk2-devel <edk2-devel@lists.01.org>
Subject: flat mapping vs identity mapping on ARM
Date: Thu, 22 Sep 2016 17:30:49 +0300 [thread overview]
Message-ID: <CANPuzFxJhYPRv16o0Z1w0F0c22mvzo6sW6hGm43qEOZ4U8LRoQ@mail.gmail.com> (raw)
In the ARM architecture, there is such a thing - "flat mapping", where
MMU stage 1 is disabled and the mapping done is 1:1 and attributes set
to the predefined values.
Did I understand right, that this is NOT what UEFI means by "identity
mapping" with MMU enabled? And in the latter case there is need to
create all those page tables and stuff, setting 1:1 mapping between VA
and PA? If so, why to do that? Why "flat mapping" isn't what UEFI
would love to see as its mapping regime?
next reply other threads:[~2016-09-22 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 14:30 valerij zaporogeci [this message]
2016-09-22 15:03 ` flat mapping vs identity mapping on ARM Ard Biesheuvel
2016-09-22 15:19 ` valerij zaporogeci
2016-09-22 15:22 ` Ard Biesheuvel
2016-09-22 15:23 ` Ard Biesheuvel
2016-09-22 15:34 ` Andrew Fish
2016-09-22 19:14 ` valerij zaporogeci
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-list 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=CANPuzFxJhYPRv16o0Z1w0F0c22mvzo6sW6hGm43qEOZ4U8LRoQ@mail.gmail.com \
--to=devel@edk2.groups.io \
/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