diff options
| author |   Alexander Gordeev <agordeev@linux.ibm.com> | 2023-07-11 12:21:39 +0200 |
|---|---|---|
| committer | Alexander Gordeev <agordeev@linux.ibm.com> | 2024-04-17 13:37:59 +0200 |
| commit | 47bf81767277b5abb87f7e86e15310f0e9d4d06c (patch) | |
| tree | 4a8c222a653546aa8b52112ad8c4ce0dfce5a895 /tools/perf/scripts/python | |
| parent | KVM: s390: vsie: Use virt_to_phys for facility control block (diff) | |
| download | wireguard-linux-47bf81767277b5abb87f7e86e15310f0e9d4d06c.tar.xz wireguard-linux-47bf81767277b5abb87f7e86e15310f0e9d4d06c.zip | |
s390/boot: Do not force vmemmap to start at MAX_PHYSMEM_BITS
vmemmap is forcefully set to start at MAX_PHYSMEM_BITS at most.
That could be needed in the past to limit ident_map_size to
MAX_PHYSMEM_BITS. However since commit 75eba6ec0de1 ("s390:
unify identity mapping limits handling") ident_map_size is
limited in setup_ident_map_size() function, which is called
earlier.
Another reason to limit vmemmap start to MAX_PHYSMEM_BITS is
because it was returned by arch_get_mappable_range() as the
maximum mappable physical address. Since commit f641679dfe55
("s390/mm: rework arch_get_mappable_range() callback") that
is not required anymore.
As result, there is no neccessity to limit vmemmap starting
address with MAX_PHYSMEM_BITS.
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Alexander Gordeev <agordeev@linux.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions