PF_IO_WORKER are kernel threads too, but they aren't PF_KTHREAD in the sense that we don't assign ->set_child_tid with our own structure. Just ensure that every arch sets up the PF_IO_WORKER threads like kthreads in the arch implementation of copy_thread(). Signed-off-by: Jens Axboe <axboe@kernel.dk> |
||
|---|---|---|
| .. | ||
| asm-offsets.c | ||
| dma.c | ||
| head.S | ||
| hexagon_ksyms.c | ||
| irq_cpu.c | ||
| kgdb.c | ||
| Makefile | ||
| module.c | ||
| process.c | ||
| ptrace.c | ||
| reset.c | ||
| screen_info.c | ||
| setup.c | ||
| signal.c | ||
| smp.c | ||
| stacktrace.c | ||
| syscalltab.c | ||
| time.c | ||
| trampoline.S | ||
| traps.c | ||
| vdso.c | ||
| vm_entry.S | ||
| vm_events.c | ||
| vm_init_segtable.S | ||
| vm_ops.S | ||
| vm_switch.S | ||
| vm_vectors.S | ||
| vmlinux.lds.S | ||