diff options
| author | Vasily Gorbik <gor@linux.ibm.com> | 2020-10-15 11:20:08 +0300 |
|---|---|---|
| committer | Heiko Carstens <hca@linux.ibm.com> | 2020-11-09 13:20:58 +0300 |
| commit | 97b142b7400bdce93aa674df044a4bc58e88f08c (patch) | |
| tree | 0e5804927b127f16ebf614a1d749cab1762358c9 /Kconfig | |
| parent | a3453d923ece6760689894bad5b6d5e00c0ffe2d (diff) | |
| download | linux-97b142b7400bdce93aa674df044a4bc58e88f08c.tar.xz | |
s390: make sure vmemmap is top region table entry aligned
Since commit 29d37e5b82f3 ("s390/protvirt: add ultravisor initialization")
vmax is adjusted to the ultravisor secure storage limit. This limit is
currently applied when 4-level paging is used. Later vmax is also used
to align vmemmap address to the top region table entry border. When vmax
is set to the ultravisor secure storage limit this is no longer the case.
Instead of changing vmax, make only MODULES_END be affected by the
secure storage limit, so that vmax stays intact for further vmemmap
address alignment.
Reviewed-by: Alexander Gordeev <agordeev@linux.ibm.com>
Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions