arm64: mm: Introduce MAX_USER_VA_BITS definition

Browse source

With the introduction of 52-bit virtual addressing for userspace, we are
now in a position where the virtual addressing capability of userspace
may exceed that of the kernel. Consequently, the VA_BITS definition
cannot be used blindly, since it reflects only the size of kernel
virtual addresses.

This patch introduces MAX_USER_VA_BITS which is either VA_BITS or 52
depending on whether 52-bit virtual addressing has been configured at
build time, removing a few places where the 52 is open-coded based on
explicit CONFIG_ guards.

Signed-off-by: Will Deacon <will.deacon@arm.com>

...

This commit is contained in:

Will Deacon 2018-12-12 11:51:40 +00:00

parent 4d08d20f1c

commit 9b31cf493f

3 changed files with 8 additions and 10 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

6

arch/arm64/include/asm/memory.h

View file

6

arch/arm64/include/asm/pgtable-hwdef.h

View file

6

arch/arm64/include/asm/processor.h

View file