Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 12e55fa1 authored by Vasily Gorbik's avatar Vasily Gorbik Committed by Martin Schwidefsky
Browse files

s390/kasan: optimize kasan vmemmap allocation 



Kasan implementation now supports memory hotplug operations. For that
reason regions of initially standby memory are now skipped from
shadow mapping and are mapped/unmapped dynamically upon bringing
memory online/offline.

Signed-off-by: default avatarVasily Gorbik <gor@linux.ibm.com>
Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
parent 29635239

arch/s390/mm/kasan_init.c

+2 −1
Original line number Diff line number Diff line
@@ -331,7 +331,8 @@ void __init kasan_early_init(void) 
	kasan_early_vmemmap_populate(__sha(0), __sha(memsize), POPULATE_MAP);

	if (IS_ENABLED(CONFIG_MODULES))

		untracked_mem_end = vmax - MODULES_LEN;

	kasan_early_vmemmap_populate(__sha(memsize), __sha(untracked_mem_end),

	kasan_early_vmemmap_populate(__sha(max_physmem_end),

				     __sha(untracked_mem_end),

				     POPULATE_ZERO_SHADOW);

	/* memory allocated for identity mapping structs will be freed later */

	pgalloc_freeable = pgalloc_pos;