powerpc: differentiate kthread from user kernel thread start

Browse source

Kernel created user threads start similarly to kernel threads in that
they call a kernel function after first returning from _switch, so
they share ret_from_kernel_thread for this. Kernel threads never return
from that function though, whereas user threads often do (although some
don't, e.g., IO threads).

Split these startup functions in two, and catch kernel threads that
improperly return from their function. This is intended to make the
complicated code a little bit easier to understand.

Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230325122904.2375060-7-npiggin@gmail.com

...

This commit is contained in:

Nicholas Piggin 2023-03-25 22:29:02 +10:00 • committed by Michael Ellerman

parent eed7c420aa

commit b504b6aade

3 changed files with 39 additions and 6 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

20

arch/powerpc/kernel/entry_32.S

View file

18

arch/powerpc/kernel/interrupt_64.S

View file

7

arch/powerpc/kernel/process.c

View file