[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 02:00:09 +03:00
|
|
|
/*
|
|
|
|
* System call callback functions for SPUs
|
|
|
|
*/
|
|
|
|
|
2007-09-19 08:38:12 +04:00
|
|
|
#undef DEBUG
|
[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 02:00:09 +03:00
|
|
|
|
|
|
|
#include <linux/kallsyms.h>
|
|
|
|
#include <linux/module.h>
|
|
|
|
#include <linux/syscalls.h>
|
|
|
|
|
|
|
|
#include <asm/spu.h>
|
|
|
|
#include <asm/syscalls.h>
|
|
|
|
#include <asm/unistd.h>
|
|
|
|
|
|
|
|
/*
|
|
|
|
* This table defines the system calls that an SPU can call.
|
|
|
|
* It is currently a subset of the 64 bit powerpc system calls,
|
|
|
|
* with the exact semantics.
|
|
|
|
*
|
|
|
|
* The reasons for disabling some of the system calls are:
|
|
|
|
* 1. They interact with the way SPU syscalls are handled
|
|
|
|
* and we can't let them execute ever:
|
|
|
|
* restart_syscall, exit, for, execve, ptrace, ...
|
|
|
|
* 2. They are deprecated and replaced by other means:
|
|
|
|
* uselib, pciconfig_*, sysfs, ...
|
|
|
|
* 3. They are somewhat interacting with the system in a way
|
|
|
|
* we don't want an SPU to:
|
|
|
|
* reboot, init_module, mount, kexec_load
|
|
|
|
* 4. They are optional and we can't rely on them being
|
|
|
|
* linked into the kernel. Unfortunately, the cond_syscall
|
|
|
|
* helper does not work here as it does not add the necessary
|
|
|
|
* opd symbols:
|
|
|
|
* mbind, mq_open, ipc, ...
|
|
|
|
*/
|
|
|
|
|
2007-09-19 08:38:12 +04:00
|
|
|
static void *spu_syscall_table[] = {
|
2006-06-20 00:45:04 +04:00
|
|
|
#define SYSCALL(func) sys_ni_syscall,
|
|
|
|
#define COMPAT_SYS(func) sys_ni_syscall,
|
|
|
|
#define PPC_SYS(func) sys_ni_syscall,
|
|
|
|
#define OLDSYS(func) sys_ni_syscall,
|
|
|
|
#define SYS32ONLY(func) sys_ni_syscall,
|
|
|
|
#define SYSX(f, f3264, f32) sys_ni_syscall,
|
|
|
|
|
|
|
|
#define SYSCALL_SPU(func) sys_##func,
|
|
|
|
#define COMPAT_SYS_SPU(func) sys_##func,
|
|
|
|
#define PPC_SYS_SPU(func) ppc_##func,
|
|
|
|
#define SYSX_SPU(f, f3264, f32) f,
|
|
|
|
|
|
|
|
#include <asm/systbl.h>
|
[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 02:00:09 +03:00
|
|
|
};
|
|
|
|
|
|
|
|
long spu_sys_callback(struct spu_syscall_block *s)
|
|
|
|
{
|
|
|
|
long (*syscall)(u64 a1, u64 a2, u64 a3, u64 a4, u64 a5, u64 a6);
|
|
|
|
|
2006-04-18 17:24:16 +04:00
|
|
|
if (s->nr_ret >= ARRAY_SIZE(spu_syscall_table)) {
|
2009-01-06 17:26:03 +03:00
|
|
|
pr_debug("%s: invalid syscall #%lld", __func__, s->nr_ret);
|
[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 02:00:09 +03:00
|
|
|
return -ENOSYS;
|
|
|
|
}
|
|
|
|
|
2006-05-23 18:46:39 +04:00
|
|
|
syscall = spu_syscall_table[s->nr_ret];
|
|
|
|
|
[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 02:00:09 +03:00
|
|
|
#ifdef DEBUG
|
|
|
|
print_symbol(KERN_DEBUG "SPU-syscall %s:", (unsigned long)syscall);
|
|
|
|
printk("syscall%ld(%lx, %lx, %lx, %lx, %lx, %lx)\n",
|
|
|
|
s->nr_ret,
|
|
|
|
s->parm[0], s->parm[1], s->parm[2],
|
|
|
|
s->parm[3], s->parm[4], s->parm[5]);
|
|
|
|
#endif
|
|
|
|
|
|
|
|
return syscall(s->parm[0], s->parm[1], s->parm[2],
|
|
|
|
s->parm[3], s->parm[4], s->parm[5]);
|
|
|
|
}
|
|
|
|
EXPORT_SYMBOL_GPL(spu_sys_callback);
|