diff options
author | Ard Biesheuvel <[email protected]> | 2020-10-08 17:36:01 +0200 |
---|---|---|
committer | Catalin Marinas <[email protected]> | 2020-11-09 17:15:37 +0000 |
commit | 8c96400d6a39be763130a5c493647c57726f7013 (patch) | |
tree | 0794db8f11e674731069015b34a5c593f8a77ac7 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | f4693c2716b35d0846fd45a4ad7db78bfb25efc8 (diff) |
arm64: mm: make vmemmap region a projection of the linear region
Now that we have reverted the introduction of the vmemmap struct page
pointer and the separate physvirt_offset, we can simplify things further,
and place the vmemmap region in the VA space in such a way that virtual
to page translations and vice versa can be implemented using a single
arithmetic shift.
One happy coincidence resulting from this is that the 48-bit/4k and
52-bit/64k configurations (which are assumed to be the two most
prevalent) end up with the same placement of the vmemmap region. In
a subsequent patch, we will take advantage of this, and unify the
memory maps even more.
Signed-off-by: Ard Biesheuvel <[email protected]>
Reviewed-by: Steve Capper <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Catalin Marinas <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions