2005-11-01 09:08:41 +08:00
|
|
|
obj-y += interrupt.o iommu.o setup.o spider-pic.o
|
2006-01-05 03:55:53 +08:00
|
|
|
obj-y += pervasive.o
|
|
|
|
|
|
2005-11-01 09:08:38 +08:00
|
|
|
obj-$(CONFIG_SMP) += smp.o
|
2006-01-24 09:37:11 +08:00
|
|
|
obj-$(CONFIG_SPU_FS) += spu-base.o spufs/
|
2006-01-05 03:31:30 +08:00
|
|
|
|
|
|
|
|
spu-base-y += spu_base.o spu_priv1.o
|
|
|
|
|
|
[PATCH] spufs: allow SPU code to do syscalls
An SPU does not have a way to implement system calls
itself, but it can create intercepts to the kernel.
This patch uses the method defined by the JSRE interface
for C99 host library calls from an SPU to implement
Linux system calls. It uses the reserved SPU stop code
0x2104 for this, using the structure layout and syscall
numbers for ppc64-linux.
I'm still undecided wether it is better to have a list
of allowed syscalls or a list of forbidden syscalls,
since we can't allow an SPU to call all syscalls that
are defined for ppc64-linux.
This patch implements the easier choice of them, with a
blacklist that only prevents an SPU from calling anything
that interacts with its own execution, e.g fork, execve,
clone, vfork, exit, spu_run and spu_create and everything
that deals with signals.
Signed-off-by: Arnd Bergmann <arnd.bergmann@de.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
2006-03-23 07:00:09 +08:00
|
|
|
# needed only when building loadable spufs.ko
|
|
|
|
|
spufs-modular-$(CONFIG_SPU_FS) += spu_syscalls.o
|
|
|
|
|
obj-y += $(spufs-modular-m)
|
|
|
|
|
|
|
|
|
|
# always needed in kernel
|
|
|
|
|
spufs-builtin-$(CONFIG_SPU_FS) += spu_callbacks.o
|
|
|
|
|
obj-y += $(spufs-builtin-y) $(spufs-builtin-m)
|
|
|
|
|
|
