0111a70186
At present, we have a situation where a context with no owner is re-scheduled by spu_forget: Thread 1: reading regs file Thread 2: context owner spu_forget() - ctx->owner = NULL - set SPU_SCHED_WAS_ACTIVE spu_acquire_saved() - context is in saved state spu_release_saved() - SPU_SCHED_WAS_ACTIVE is set, so spu_activate() the context, which now has no owner In spu_forget(), we shouldn't be requesting a re-schedule by setting SPU_SCHED_WAS_ACTIVE. This change removes the set_bit in spu_forget(), so that spu_release_saved() doesn't reinsert this destroyed context on to the run queue. Signed-off-by: Jeremy Kerr <jk@ozlabs.org> |
||
|---|---|---|
| .. | ||
| backing_ops.c | ||
| context.c | ||
| coredump.c | ||
| fault.c | ||
| file.c | ||
| gang.c | ||
| hw_ops.c | ||
| inode.c | ||
| lscsa_alloc.c | ||
| Makefile | ||
| run.c | ||
| sched.c | ||
| spu_restore_crt0.S | ||
| spu_restore_dump.h_shipped | ||
| spu_restore.c | ||
| spu_save_crt0.S | ||
| spu_save_dump.h_shipped | ||
| spu_save.c | ||
| spu_utils.h | ||
| spufs.h | ||
| sputrace.c | ||
| switch.c | ||
| syscalls.c | ||