Searched hist:"3 afdfca69870963ae01e280732a5ee493a2fcbb3" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/arch/s390/include/asm/ |
H A D | hugetlb.h | diff 3afdfca69870963ae01e280732a5ee493a2fcbb3 Fri Jul 13 05:28:26 CDT 2018 Janosch Frank <frankja@linux.ibm.com> s390/mm: Clear skeys for newly mapped huge guest pmds
Similarly to the pte skey handling, where we set the storage key to the default key for each newly mapped pte, we have to also do that for huge pmds.
With the PG_arch_1 flag we keep track if the area has already been cleared of its skeys.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com> Reviewed-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
/openbmc/linux/arch/s390/mm/ |
H A D | hugetlbpage.c | diff 3afdfca69870963ae01e280732a5ee493a2fcbb3 Fri Jul 13 05:28:26 CDT 2018 Janosch Frank <frankja@linux.ibm.com> s390/mm: Clear skeys for newly mapped huge guest pmds
Similarly to the pte skey handling, where we set the storage key to the default key for each newly mapped pte, we have to also do that for huge pmds.
With the PG_arch_1 flag we keep track if the area has already been cleared of its skeys.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com> Reviewed-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|
H A D | gmap.c | diff 3afdfca69870963ae01e280732a5ee493a2fcbb3 Fri Jul 13 05:28:26 CDT 2018 Janosch Frank <frankja@linux.ibm.com> s390/mm: Clear skeys for newly mapped huge guest pmds
Similarly to the pte skey handling, where we set the storage key to the default key for each newly mapped pte, we have to also do that for huge pmds.
With the PG_arch_1 flag we keep track if the area has already been cleared of its skeys.
Signed-off-by: Janosch Frank <frankja@linux.ibm.com> Reviewed-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
|