On Fri, 25 Aug 2023 11:49:10 +1000, Benjamin Gray wrote:
> To determine if a trap was caused by a HASHCHK instruction, we inspect
> the user instruction that triggered the trap. However this may sleep
> if the page needs to be faulted in.
>
> Move the HASHCHK handler logic to after we allow IRQs, which is fine
> because we are only interested in HASHCHK if it's a user space trap.
>
> [...]
Applied to powerpc/fixes.
[1/1] powerpc/dexcr: Move HASHCHK trap handler
https://git.kernel.org/powerpc/c/c3f4309693758b13fbb34b3741c2e2801ad28769
cheers
