diff options
| author |   Vasily Gorbik <gor@linux.ibm.com> | 2021-10-14 13:45:35 +0200 |
|---|---|---|
| committer |   Heiko Carstens <hca@linux.ibm.com> | 2021-11-16 12:29:19 +0100 |
| commit | 6ad5f024d1f5612b9e39ced9f1add6e8121a7afb (patch) | |
| tree | 89fb93dccc8c10369bcad1304808b7243bc31b9f /arch/s390/Kconfig | |
| parent | s390/setup: avoid using memblock_enforce_memory_limit (diff) | |
| download | linux-dev-6ad5f024d1f5612b9e39ced9f1add6e8121a7afb.tar.xz linux-dev-6ad5f024d1f5612b9e39ced9f1add6e8121a7afb.zip | |
s390/setup: re-arrange memblock setup
- Avoid using ULONG_MAX in memblock_remove, it has no functional change
but makes memblock_dbg output a range which makes sense.
- Actually finish memblock memory setup before doing amode31/cr/uv
setup.
- Move memblock_dump_all() debug output after memblock memory setup is
complete. This gives us final "memory" regions if they were trimmed
due to addressing limits and still "physmem" regions as original info
which came from mem_detect.
Reviewed-by: Heiko Carstens <hca@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'arch/s390/Kconfig')
0 files changed, 0 insertions, 0 deletions