Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-03-22 Thread Michael Ellerman
Nicholas Piggin writes: > Excerpts from Michael Ellerman's message of March 16, 2021 4:40 pm: >> Nicholas Piggin writes: >>> Excerpts from Michael Ellerman's message of February 11, 2021 11:51 pm: When we enabled STRICT_KERNEL_RWX we received some reports of boot failures when using the

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-03-21 Thread Nicholas Piggin
Excerpts from Michael Ellerman's message of March 16, 2021 4:40 pm: > Nicholas Piggin writes: >> Excerpts from Michael Ellerman's message of February 11, 2021 11:51 pm: >>> When we enabled STRICT_KERNEL_RWX we received some reports of boot >>> failures when using the Hash MMU and running under phy

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-03-21 Thread Nicholas Piggin
Excerpts from Michael Ellerman's message of March 20, 2021 11:04 pm: > Nicholas Piggin writes: >> Excerpts from Michael Ellerman's message of February 11, 2021 11:51 pm: > ... >>> diff --git a/arch/powerpc/mm/book3s64/hash_pgtable.c >>> b/arch/powerpc/mm/book3s64/hash_pgtable.c >>> index 3663d3cd

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-03-20 Thread Michael Ellerman
Nicholas Piggin writes: > Excerpts from Michael Ellerman's message of February 11, 2021 11:51 pm: ... >> diff --git a/arch/powerpc/mm/book3s64/hash_pgtable.c >> b/arch/powerpc/mm/book3s64/hash_pgtable.c >> index 3663d3cdffac..01de985df2c4 100644 >> --- a/arch/powerpc/mm/book3s64/hash_pgtable.c >>

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-03-19 Thread Michael Ellerman
Daniel Axtens writes: > Michael Ellerman writes: > >> When we enabled STRICT_KERNEL_RWX we received some reports of boot >> failures when using the Hash MMU and running under phyp. The crashes >> are intermittent, and often exhibit as a completely unresponsive >> system, or possibly an oops. >> >

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-03-15 Thread Michael Ellerman
Nicholas Piggin writes: > Excerpts from Michael Ellerman's message of February 11, 2021 11:51 pm: >> When we enabled STRICT_KERNEL_RWX we received some reports of boot >> failures when using the Hash MMU and running under phyp. The crashes >> are intermittent, and often exhibit as a completely unr

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-02-18 Thread Daniel Axtens
Michael Ellerman writes: > When we enabled STRICT_KERNEL_RWX we received some reports of boot > failures when using the Hash MMU and running under phyp. The crashes > are intermittent, and often exhibit as a completely unresponsive > system, or possibly an oops. > > One example, which was caught

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-02-11 Thread Nicholas Piggin
Excerpts from Michael Ellerman's message of February 11, 2021 11:51 pm: > When we enabled STRICT_KERNEL_RWX we received some reports of boot > failures when using the Hash MMU and running under phyp. The crashes > are intermittent, and often exhibit as a completely unresponsive > system, or possibl

Re: [PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-02-11 Thread Nicholas Piggin
Excerpts from Michael Ellerman's message of February 11, 2021 11:51 pm: > When we enabled STRICT_KERNEL_RWX we received some reports of boot > failures when using the Hash MMU and running under phyp. The crashes > are intermittent, and often exhibit as a completely unresponsive > system, or possibl

[PATCH 5/6] powerpc/mm/64s/hash: Add real-mode change_memory_range() for hash LPAR

2021-02-11 Thread Michael Ellerman
When we enabled STRICT_KERNEL_RWX we received some reports of boot failures when using the Hash MMU and running under phyp. The crashes are intermittent, and often exhibit as a completely unresponsive system, or possibly an oops. One example, which was caught in xmon: [ 14.068327][T1] dev