Searched hist:af5ca9d5c8b45244b237d7a5534e1ec2d01cce8e (Results 1 – 3 of 3) sorted by relevance
| /linux/arch/powerpc/kernel/ |
| H A D | interrupt_64.S | diff af5ca9d5c8b45244b237d7a5534e1ec2d01cce8e Sat Mar 25 13:28:59 CET 2023 Nicholas Piggin <npiggin@gmail.com> powerpc: use switch frame for ret_from_kernel_thread parameters
The kernel thread path in copy_thread creates a user interrupt frame on
stack and stores the function and arg parameters there, and
ret_from_kernel_thread loads them. This is a slightly confusing way to
overload that frame. Non-volatile registers are loaded from the switch
frame, so the parameters can be stored there. The user interrupt frame
is now only used by user threads when they return to user.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230325122904.2375060-4-npiggin@gmail.com
|
| H A D | entry_32.S | diff af5ca9d5c8b45244b237d7a5534e1ec2d01cce8e Sat Mar 25 13:28:59 CET 2023 Nicholas Piggin <npiggin@gmail.com> powerpc: use switch frame for ret_from_kernel_thread parameters
The kernel thread path in copy_thread creates a user interrupt frame on
stack and stores the function and arg parameters there, and
ret_from_kernel_thread loads them. This is a slightly confusing way to
overload that frame. Non-volatile registers are loaded from the switch
frame, so the parameters can be stored there. The user interrupt frame
is now only used by user threads when they return to user.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230325122904.2375060-4-npiggin@gmail.com
|
| H A D | process.c | diff af5ca9d5c8b45244b237d7a5534e1ec2d01cce8e Sat Mar 25 13:28:59 CET 2023 Nicholas Piggin <npiggin@gmail.com> powerpc: use switch frame for ret_from_kernel_thread parameters
The kernel thread path in copy_thread creates a user interrupt frame on
stack and stores the function and arg parameters there, and
ret_from_kernel_thread loads them. This is a slightly confusing way to
overload that frame. Non-volatile registers are loaded from the switch
frame, so the parameters can be stored there. The user interrupt frame
is now only used by user threads when they return to user.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230325122904.2375060-4-npiggin@gmail.com
|