You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Arnd Bergmann 57dace2391 [POWERPC] spufs: make spu page faults not block scheduling ... Until now, we have always entered the spu page fault handler with a mutex for the spu context held. This has multiple bad side-effects: - it becomes impossible to suspend the context during page faults - if an spu program attempts to access its own mmio areas through DMA, we get an immediate livelock when the nopage function tries to acquire the same mutex This patch makes the page fault logic operate on a struct spu_context instead of a struct spu, and moves it from spu_base.c to a new file fault.c inside of spufs. We now also need to copy the dar and dsisr contents of the last fault into the saved context to have it accessible in case we schedule out the context before activating the page fault handler. Signed-off-by: Arnd Bergmann <arnd.bergmann@de.ibm.com>		18 years ago
..
Makefile	[POWERPC] spufs: make spu page faults not block scheduling	18 years ago
backing_ops.c	[POWERPC] spufs: make spu page faults not block scheduling	18 years ago
context.c	…
coredump.c	…
fault.c	[POWERPC] spufs: make spu page faults not block scheduling	18 years ago
file.c	…
gang.c	…
hw_ops.c	[POWERPC] spufs: make spu page faults not block scheduling	18 years ago
inode.c	…
run.c	[POWERPC] spufs: make spu page faults not block scheduling	18 years ago
sched.c	…
spu_restore.c	…
spu_restore_crt0.S	…
spu_restore_dump.h_shipped	…
spu_save.c	…
spu_save_crt0.S	…
spu_save_dump.h_shipped	…
spu_utils.h	…
spufs.h	[POWERPC] spufs: make spu page faults not block scheduling	18 years ago
switch.c	[POWERPC] spufs: make spu page faults not block scheduling	18 years ago
syscalls.c	…