7ec18ab923
For quite a while now spu state is protected by a simple mutex instead of the old rw_semaphore, and this means we can simplify the locking around spu_setup_isolated a lot. Instead of doing an spu_release before entering spu_setup_isolated and then calling the complicated spu_acquire_exclusive we can now simply enter the function locked an in guaranteed runnable state, so that the only bit of spu_acquire_exclusive that's left is the call to spu_unmap_mappings. Similarly there's no more need to unlock and reacquire the state_mutex when spu_setup_isolated is done, but we can always return with the lock held and only drop it in spu_run_init in the failure case. Signed-off-by: Christoph Hellwig <hch@lst.de> Signed-off-by: Arnd Bergmann <arnd.bergmann@de.ibm.com> |
||
---|---|---|
.. | ||
backing_ops.c | ||
context.c | ||
coredump.c | ||
file.c | ||
gang.c | ||
hw_ops.c | ||
inode.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 | ||
switch.c | ||
syscalls.c |