2006-10-25 00:31:18 +08:00
|
|
|
#define DEBUG
|
|
|
|
|
2006-01-05 03:31:29 +08:00
|
|
|
#include <linux/wait.h>
|
|
|
|
#include <linux/ptrace.h>
|
|
|
|
|
|
|
|
#include <asm/spu.h>
|
2006-11-21 01:45:10 +08:00
|
|
|
#include <asm/spu_priv1.h>
|
|
|
|
#include <asm/io.h>
|
2006-04-01 12:53:09 +08:00
|
|
|
#include <asm/unistd.h>
|
2006-01-05 03:31:29 +08:00
|
|
|
|
|
|
|
#include "spufs.h"
|
|
|
|
|
|
|
|
/* interrupt-level stop callback function. */
|
2008-04-28 02:41:55 +08:00
|
|
|
void spufs_stop_callback(struct spu *spu, int irq)
|
2006-01-05 03:31:29 +08:00
|
|
|
{
|
|
|
|
struct spu_context *ctx = spu->ctx;
|
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
/*
|
|
|
|
* It should be impossible to preempt a context while an exception
|
|
|
|
* is being processed, since the context switch code is specially
|
|
|
|
* coded to deal with interrupts ... But, just in case, sanity check
|
|
|
|
* the context pointer. It is OK to return doing nothing since
|
|
|
|
* the exception will be regenerated when the context is resumed.
|
|
|
|
*/
|
|
|
|
if (ctx) {
|
|
|
|
/* Copy exception arguments into module specific structure */
|
2008-04-28 02:41:55 +08:00
|
|
|
switch(irq) {
|
|
|
|
case 0 :
|
|
|
|
ctx->csa.class_0_pending = spu->class_0_pending;
|
|
|
|
ctx->csa.class_0_dar = spu->class_0_dar;
|
|
|
|
break;
|
|
|
|
case 1 :
|
|
|
|
ctx->csa.class_1_dsisr = spu->class_1_dsisr;
|
|
|
|
ctx->csa.class_1_dar = spu->class_1_dar;
|
|
|
|
break;
|
|
|
|
case 2 :
|
|
|
|
break;
|
|
|
|
}
|
2007-12-20 15:39:59 +08:00
|
|
|
|
|
|
|
/* ensure that the exception status has hit memory before a
|
|
|
|
* thread waiting on the context's stop queue is woken */
|
|
|
|
smp_wmb();
|
|
|
|
|
|
|
|
wake_up_all(&ctx->stop_wq);
|
|
|
|
}
|
2006-01-05 03:31:29 +08:00
|
|
|
}
|
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
int spu_stopped(struct spu_context *ctx, u32 *stat)
|
2006-01-05 03:31:29 +08:00
|
|
|
{
|
2007-12-20 15:39:59 +08:00
|
|
|
u64 dsisr;
|
|
|
|
u32 stopped;
|
2006-01-05 03:31:29 +08:00
|
|
|
|
2008-05-30 04:46:10 +08:00
|
|
|
stopped = SPU_STATUS_INVALID_INSTR | SPU_STATUS_SINGLE_STEP |
|
|
|
|
SPU_STATUS_STOPPED_BY_HALT | SPU_STATUS_STOPPED_BY_STOP;
|
2007-07-21 03:39:52 +08:00
|
|
|
|
2008-05-30 04:46:10 +08:00
|
|
|
top:
|
|
|
|
*stat = ctx->ops->status_read(ctx);
|
|
|
|
if (*stat & stopped) {
|
|
|
|
/*
|
|
|
|
* If the spu hasn't finished stopping, we need to
|
|
|
|
* re-read the register to get the stopped value.
|
|
|
|
*/
|
|
|
|
if (*stat & SPU_STATUS_RUNNING)
|
|
|
|
goto top;
|
2007-12-20 15:39:59 +08:00
|
|
|
return 1;
|
2008-05-30 04:46:10 +08:00
|
|
|
}
|
2007-12-20 15:39:59 +08:00
|
|
|
|
2008-05-30 04:46:10 +08:00
|
|
|
if (test_bit(SPU_SCHED_NOTIFY_ACTIVE, &ctx->sched_flags))
|
2007-12-20 15:39:59 +08:00
|
|
|
return 1;
|
|
|
|
|
2008-04-28 02:41:55 +08:00
|
|
|
dsisr = ctx->csa.class_1_dsisr;
|
2007-12-20 15:39:59 +08:00
|
|
|
if (dsisr & (MFC_DSISR_PTE_NOT_FOUND | MFC_DSISR_ACCESS_DENIED))
|
2007-07-21 03:39:52 +08:00
|
|
|
return 1;
|
2007-12-20 15:39:59 +08:00
|
|
|
|
|
|
|
if (ctx->csa.class_0_pending)
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
return 0;
|
2006-01-05 03:31:29 +08:00
|
|
|
}
|
|
|
|
|
2006-11-21 01:45:10 +08:00
|
|
|
static int spu_setup_isolated(struct spu_context *ctx)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
u64 __iomem *mfc_cntl;
|
|
|
|
u64 sr1;
|
|
|
|
u32 status;
|
|
|
|
unsigned long timeout;
|
|
|
|
const u32 status_loading = SPU_STATUS_RUNNING
|
|
|
|
| SPU_STATUS_ISOLATED_STATE | SPU_STATUS_ISOLATED_LOAD_STATUS;
|
|
|
|
|
2007-04-24 03:08:12 +08:00
|
|
|
ret = -ENODEV;
|
2006-11-21 01:45:10 +08:00
|
|
|
if (!isolated_loader)
|
|
|
|
goto out;
|
|
|
|
|
2007-04-24 03:08:12 +08:00
|
|
|
/*
|
|
|
|
* We need to exclude userspace access to the context.
|
|
|
|
*
|
|
|
|
* To protect against memory access we invalidate all ptes
|
|
|
|
* and make sure the pagefault handlers block on the mutex.
|
|
|
|
*/
|
|
|
|
spu_unmap_mappings(ctx);
|
|
|
|
|
2006-11-21 01:45:10 +08:00
|
|
|
mfc_cntl = &ctx->spu->priv2->mfc_control_RW;
|
|
|
|
|
|
|
|
/* purge the MFC DMA queue to ensure no spurious accesses before we
|
|
|
|
* enter kernel mode */
|
|
|
|
timeout = jiffies + HZ;
|
|
|
|
out_be64(mfc_cntl, MFC_CNTL_PURGE_DMA_REQUEST);
|
|
|
|
while ((in_be64(mfc_cntl) & MFC_CNTL_PURGE_DMA_STATUS_MASK)
|
|
|
|
!= MFC_CNTL_PURGE_DMA_COMPLETE) {
|
|
|
|
if (time_after(jiffies, timeout)) {
|
|
|
|
printk(KERN_ERR "%s: timeout flushing MFC DMA queue\n",
|
2008-03-29 05:21:07 +08:00
|
|
|
__func__);
|
2006-11-21 01:45:10 +08:00
|
|
|
ret = -EIO;
|
2007-04-24 03:08:12 +08:00
|
|
|
goto out;
|
2006-11-21 01:45:10 +08:00
|
|
|
}
|
|
|
|
cond_resched();
|
|
|
|
}
|
|
|
|
|
2009-02-17 08:44:14 +08:00
|
|
|
/* clear purge status */
|
|
|
|
out_be64(mfc_cntl, 0);
|
|
|
|
|
2006-11-21 01:45:10 +08:00
|
|
|
/* put the SPE in kernel mode to allow access to the loader */
|
|
|
|
sr1 = spu_mfc_sr1_get(ctx->spu);
|
|
|
|
sr1 &= ~MFC_STATE1_PROBLEM_STATE_MASK;
|
|
|
|
spu_mfc_sr1_set(ctx->spu, sr1);
|
|
|
|
|
|
|
|
/* start the loader */
|
|
|
|
ctx->ops->signal1_write(ctx, (unsigned long)isolated_loader >> 32);
|
|
|
|
ctx->ops->signal2_write(ctx,
|
|
|
|
(unsigned long)isolated_loader & 0xffffffff);
|
|
|
|
|
|
|
|
ctx->ops->runcntl_write(ctx,
|
|
|
|
SPU_RUNCNTL_RUNNABLE | SPU_RUNCNTL_ISOLATE);
|
|
|
|
|
|
|
|
ret = 0;
|
|
|
|
timeout = jiffies + HZ;
|
|
|
|
while (((status = ctx->ops->status_read(ctx)) & status_loading) ==
|
|
|
|
status_loading) {
|
|
|
|
if (time_after(jiffies, timeout)) {
|
|
|
|
printk(KERN_ERR "%s: timeout waiting for loader\n",
|
2008-03-29 05:21:07 +08:00
|
|
|
__func__);
|
2006-11-21 01:45:10 +08:00
|
|
|
ret = -EIO;
|
|
|
|
goto out_drop_priv;
|
|
|
|
}
|
|
|
|
cond_resched();
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!(status & SPU_STATUS_RUNNING)) {
|
|
|
|
/* If isolated LOAD has failed: run SPU, we will get a stop-and
|
|
|
|
* signal later. */
|
2008-03-29 05:21:07 +08:00
|
|
|
pr_debug("%s: isolated LOAD failed\n", __func__);
|
2006-11-21 01:45:10 +08:00
|
|
|
ctx->ops->runcntl_write(ctx, SPU_RUNCNTL_RUNNABLE);
|
|
|
|
ret = -EACCES;
|
2007-04-24 03:08:12 +08:00
|
|
|
goto out_drop_priv;
|
|
|
|
}
|
2006-11-21 01:45:10 +08:00
|
|
|
|
2007-04-24 03:08:12 +08:00
|
|
|
if (!(status & SPU_STATUS_ISOLATED_STATE)) {
|
2006-11-21 01:45:10 +08:00
|
|
|
/* This isn't allowed by the CBEA, but check anyway */
|
2008-03-29 05:21:07 +08:00
|
|
|
pr_debug("%s: SPU fell out of isolated mode?\n", __func__);
|
2006-11-21 01:45:10 +08:00
|
|
|
ctx->ops->runcntl_write(ctx, SPU_RUNCNTL_STOP);
|
|
|
|
ret = -EINVAL;
|
2007-04-24 03:08:12 +08:00
|
|
|
goto out_drop_priv;
|
2006-11-21 01:45:10 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
out_drop_priv:
|
|
|
|
/* Finished accessing the loader. Drop kernel mode */
|
|
|
|
sr1 |= MFC_STATE1_PROBLEM_STATE_MASK;
|
|
|
|
spu_mfc_sr1_set(ctx->spu, sr1);
|
|
|
|
|
|
|
|
out:
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2007-07-21 03:39:52 +08:00
|
|
|
static int spu_run_init(struct spu_context *ctx, u32 *npc)
|
2006-01-05 03:31:29 +08:00
|
|
|
{
|
2007-12-20 15:39:59 +08:00
|
|
|
unsigned long runcntl = SPU_RUNCNTL_RUNNABLE;
|
2007-12-20 15:39:59 +08:00
|
|
|
int ret;
|
2007-12-20 15:39:59 +08:00
|
|
|
|
2007-07-21 03:39:33 +08:00
|
|
|
spuctx_switch_state(ctx, SPU_UTIL_SYSTEM);
|
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
/*
|
|
|
|
* NOSCHED is synchronous scheduling with respect to the caller.
|
|
|
|
* The caller waits for the context to be loaded.
|
|
|
|
*/
|
|
|
|
if (ctx->flags & SPU_CREATE_NOSCHED) {
|
2007-12-20 15:39:59 +08:00
|
|
|
if (ctx->state == SPU_STATE_SAVED) {
|
|
|
|
ret = spu_activate(ctx, 0);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
|
|
|
}
|
2007-12-20 15:39:59 +08:00
|
|
|
}
|
2007-04-24 03:08:27 +08:00
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
/*
|
|
|
|
* Apply special setup as required.
|
|
|
|
*/
|
|
|
|
if (ctx->flags & SPU_CREATE_ISOLATE) {
|
2006-11-21 01:45:10 +08:00
|
|
|
if (!(ctx->ops->status_read(ctx) & SPU_STATUS_ISOLATED_STATE)) {
|
2007-12-20 15:39:59 +08:00
|
|
|
ret = spu_setup_isolated(ctx);
|
2007-04-24 03:08:12 +08:00
|
|
|
if (ret)
|
2007-04-24 03:08:27 +08:00
|
|
|
return ret;
|
2006-11-21 01:45:10 +08:00
|
|
|
}
|
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
/*
|
|
|
|
* If userspace has set the runcntrl register (eg, to
|
|
|
|
* issue an isolated exit), we need to re-set it here
|
|
|
|
*/
|
2006-11-21 01:45:10 +08:00
|
|
|
runcntl = ctx->ops->runcntl_read(ctx) &
|
|
|
|
(SPU_RUNCNTL_RUNNABLE | SPU_RUNCNTL_ISOLATE);
|
|
|
|
if (runcntl == 0)
|
|
|
|
runcntl = SPU_RUNCNTL_RUNNABLE;
|
2007-02-14 04:54:29 +08:00
|
|
|
} else {
|
2007-12-20 15:39:59 +08:00
|
|
|
unsigned long privcntl;
|
|
|
|
|
2007-06-04 13:15:37 +08:00
|
|
|
if (test_thread_flag(TIF_SINGLESTEP))
|
2007-12-20 15:39:59 +08:00
|
|
|
privcntl = SPU_PRIVCNTL_MODE_SINGLE_STEP;
|
|
|
|
else
|
|
|
|
privcntl = SPU_PRIVCNTL_MODE_NORMAL;
|
|
|
|
|
|
|
|
ctx->ops->privcntl_write(ctx, privcntl);
|
2008-08-13 09:29:31 +08:00
|
|
|
ctx->ops->npc_write(ctx, *npc);
|
|
|
|
}
|
|
|
|
|
|
|
|
ctx->ops->runcntl_write(ctx, runcntl);
|
|
|
|
|
|
|
|
if (ctx->flags & SPU_CREATE_NOSCHED) {
|
|
|
|
spuctx_switch_state(ctx, SPU_UTIL_USER);
|
|
|
|
} else {
|
2006-11-21 01:45:10 +08:00
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
if (ctx->state == SPU_STATE_SAVED) {
|
|
|
|
ret = spu_activate(ctx, 0);
|
|
|
|
if (ret)
|
|
|
|
return ret;
|
2007-12-20 15:39:59 +08:00
|
|
|
} else {
|
|
|
|
spuctx_switch_state(ctx, SPU_UTIL_USER);
|
2007-12-20 15:39:59 +08:00
|
|
|
}
|
|
|
|
}
|
2007-07-21 03:39:33 +08:00
|
|
|
|
2008-03-04 17:17:02 +08:00
|
|
|
set_bit(SPU_SCHED_SPU_RUN, &ctx->sched_flags);
|
2007-04-24 03:08:27 +08:00
|
|
|
return 0;
|
2006-01-05 03:31:29 +08:00
|
|
|
}
|
|
|
|
|
2007-07-21 03:39:52 +08:00
|
|
|
static int spu_run_fini(struct spu_context *ctx, u32 *npc,
|
|
|
|
u32 *status)
|
2006-01-05 03:31:29 +08:00
|
|
|
{
|
|
|
|
int ret = 0;
|
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
spu_del_from_rq(ctx);
|
|
|
|
|
2006-01-05 03:31:29 +08:00
|
|
|
*status = ctx->ops->status_read(ctx);
|
|
|
|
*npc = ctx->ops->npc_read(ctx);
|
2007-07-21 03:39:33 +08:00
|
|
|
|
|
|
|
spuctx_switch_state(ctx, SPU_UTIL_IDLE_LOADED);
|
2008-03-04 17:17:02 +08:00
|
|
|
clear_bit(SPU_SCHED_SPU_RUN, &ctx->sched_flags);
|
2008-10-16 07:03:46 +08:00
|
|
|
spu_switch_log_notify(NULL, ctx, SWITCH_LOG_EXIT, *status);
|
2006-01-05 03:31:29 +08:00
|
|
|
spu_release(ctx);
|
|
|
|
|
|
|
|
if (signal_pending(current))
|
|
|
|
ret = -ERESTARTSYS;
|
2006-11-21 01:45:04 +08:00
|
|
|
|
2006-01-05 03:31:29 +08:00
|
|
|
return 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 07:00:09 +08:00
|
|
|
/*
|
|
|
|
* SPU syscall restarting is tricky because we violate the basic
|
|
|
|
* assumption that the signal handler is running on the interrupted
|
|
|
|
* thread. Here instead, the handler runs on PowerPC user space code,
|
|
|
|
* while the syscall was called from the SPU.
|
|
|
|
* This means we can only do a very rough approximation of POSIX
|
|
|
|
* signal semantics.
|
|
|
|
*/
|
2007-09-19 12:38:12 +08:00
|
|
|
static int spu_handle_restartsys(struct spu_context *ctx, long *spu_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 07:00:09 +08:00
|
|
|
unsigned int *npc)
|
|
|
|
{
|
|
|
|
int ret;
|
|
|
|
|
|
|
|
switch (*spu_ret) {
|
|
|
|
case -ERESTARTSYS:
|
|
|
|
case -ERESTARTNOINTR:
|
|
|
|
/*
|
|
|
|
* Enter the regular syscall restarting for
|
|
|
|
* sys_spu_run, then restart the SPU syscall
|
|
|
|
* callback.
|
|
|
|
*/
|
|
|
|
*npc -= 8;
|
|
|
|
ret = -ERESTARTSYS;
|
|
|
|
break;
|
|
|
|
case -ERESTARTNOHAND:
|
|
|
|
case -ERESTART_RESTARTBLOCK:
|
|
|
|
/*
|
|
|
|
* Restart block is too hard for now, just return -EINTR
|
|
|
|
* to the SPU.
|
|
|
|
* ERESTARTNOHAND comes from sys_pause, we also return
|
|
|
|
* -EINTR from there.
|
|
|
|
* Assume that we need to be restarted ourselves though.
|
|
|
|
*/
|
|
|
|
*spu_ret = -EINTR;
|
|
|
|
ret = -ERESTARTSYS;
|
|
|
|
break;
|
|
|
|
default:
|
|
|
|
printk(KERN_WARNING "%s: unexpected return code %ld\n",
|
2008-03-29 05:21:07 +08:00
|
|
|
__func__, *spu_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 07:00:09 +08:00
|
|
|
ret = 0;
|
|
|
|
}
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2007-09-19 12:38:12 +08:00
|
|
|
static int spu_process_callback(struct spu_context *ctx)
|
[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
|
|
|
{
|
|
|
|
struct spu_syscall_block s;
|
|
|
|
u32 ls_pointer, npc;
|
2007-04-24 03:08:22 +08:00
|
|
|
void __iomem *ls;
|
[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
|
|
|
long spu_ret;
|
2008-04-23 14:02:10 +08:00
|
|
|
int 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 07:00:09 +08:00
|
|
|
|
|
|
|
/* get syscall block from local store */
|
2007-04-24 03:08:22 +08:00
|
|
|
npc = ctx->ops->npc_read(ctx) & ~3;
|
|
|
|
ls = (void __iomem *)ctx->ops->get_ls(ctx);
|
|
|
|
ls_pointer = in_be32(ls + npc);
|
[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
|
|
|
if (ls_pointer > (LS_SIZE - sizeof(s)))
|
|
|
|
return -EFAULT;
|
2007-04-24 03:08:22 +08:00
|
|
|
memcpy_fromio(&s, ls + ls_pointer, sizeof(s));
|
[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
|
|
|
|
|
|
|
/* do actual syscall without pinning the spu */
|
|
|
|
ret = 0;
|
|
|
|
spu_ret = -ENOSYS;
|
|
|
|
npc += 4;
|
|
|
|
|
|
|
|
if (s.nr_ret < __NR_syscalls) {
|
|
|
|
spu_release(ctx);
|
|
|
|
/* do actual system call from here */
|
|
|
|
spu_ret = spu_sys_callback(&s);
|
|
|
|
if (spu_ret <= -ERESTARTSYS) {
|
|
|
|
ret = spu_handle_restartsys(ctx, &spu_ret, &npc);
|
|
|
|
}
|
2008-04-23 14:02:10 +08:00
|
|
|
mutex_lock(&ctx->state_mutex);
|
[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
|
|
|
if (ret == -ERESTARTSYS)
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2008-03-25 10:32:03 +08:00
|
|
|
/* need to re-get the ls, as it may have changed when we released the
|
|
|
|
* spu */
|
|
|
|
ls = (void __iomem *)ctx->ops->get_ls(ctx);
|
|
|
|
|
[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
|
|
|
/* write result, jump over indirect pointer */
|
2007-04-24 03:08:22 +08:00
|
|
|
memcpy_toio(ls + ls_pointer, &spu_ret, sizeof(spu_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 07:00:09 +08:00
|
|
|
ctx->ops->npc_write(ctx, npc);
|
|
|
|
ctx->ops->runcntl_write(ctx, SPU_RUNCNTL_RUNNABLE);
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2007-07-21 03:39:42 +08:00
|
|
|
long spufs_run_spu(struct spu_context *ctx, u32 *npc, u32 *event)
|
2006-01-05 03:31:29 +08:00
|
|
|
{
|
|
|
|
int ret;
|
2007-07-21 03:39:52 +08:00
|
|
|
struct spu *spu;
|
2006-10-04 23:26:14 +08:00
|
|
|
u32 status;
|
2006-01-05 03:31:29 +08:00
|
|
|
|
2007-04-24 03:08:17 +08:00
|
|
|
if (mutex_lock_interruptible(&ctx->run_mutex))
|
2006-01-05 03:31:29 +08:00
|
|
|
return -ERESTARTSYS;
|
|
|
|
|
2006-10-04 23:26:14 +08:00
|
|
|
ctx->event_return = 0;
|
2007-04-24 03:08:27 +08:00
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
ret = spu_acquire(ctx);
|
|
|
|
if (ret)
|
|
|
|
goto out_unlock;
|
2007-06-29 08:57:55 +08:00
|
|
|
|
2008-04-23 12:24:27 +08:00
|
|
|
spu_enable_spu(ctx);
|
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
spu_update_sched_info(ctx);
|
2007-04-24 03:08:27 +08:00
|
|
|
|
|
|
|
ret = spu_run_init(ctx, npc);
|
|
|
|
if (ret) {
|
|
|
|
spu_release(ctx);
|
2006-01-05 03:31:29 +08:00
|
|
|
goto out;
|
2007-04-24 03:08:27 +08:00
|
|
|
}
|
2006-01-05 03:31:29 +08:00
|
|
|
|
|
|
|
do {
|
2006-10-04 23:26:14 +08:00
|
|
|
ret = spufs_wait(ctx->stop_wq, spu_stopped(ctx, &status));
|
2008-02-08 12:50:41 +08:00
|
|
|
if (unlikely(ret)) {
|
|
|
|
/*
|
|
|
|
* This is nasty: we need the state_mutex for all the
|
|
|
|
* bookkeeping even if the syscall was interrupted by
|
|
|
|
* a signal. ewww.
|
|
|
|
*/
|
|
|
|
mutex_lock(&ctx->state_mutex);
|
2006-01-05 03:31:29 +08:00
|
|
|
break;
|
2008-02-08 12:50:41 +08:00
|
|
|
}
|
2007-07-21 03:39:52 +08:00
|
|
|
spu = ctx->spu;
|
|
|
|
if (unlikely(test_and_clear_bit(SPU_SCHED_NOTIFY_ACTIVE,
|
|
|
|
&ctx->sched_flags))) {
|
|
|
|
if (!(status & SPU_STATUS_STOPPED_BY_STOP)) {
|
|
|
|
spu_switch_notify(spu, ctx);
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
}
|
2007-07-21 03:39:33 +08:00
|
|
|
|
|
|
|
spuctx_switch_state(ctx, SPU_UTIL_SYSTEM);
|
|
|
|
|
2006-10-04 23:26:14 +08:00
|
|
|
if ((status & SPU_STATUS_STOPPED_BY_STOP) &&
|
|
|
|
(status >> SPU_STOP_STATUS_SHIFT == 0x2104)) {
|
[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
|
|
|
ret = spu_process_callback(ctx);
|
|
|
|
if (ret)
|
|
|
|
break;
|
2006-10-04 23:26:14 +08:00
|
|
|
status &= ~SPU_STATUS_STOPPED_BY_STOP;
|
[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
|
|
|
}
|
2007-04-24 03:08:15 +08:00
|
|
|
ret = spufs_handle_class1(ctx);
|
|
|
|
if (ret)
|
|
|
|
break;
|
|
|
|
|
2007-12-20 15:39:59 +08:00
|
|
|
ret = spufs_handle_class0(ctx);
|
|
|
|
if (ret)
|
|
|
|
break;
|
|
|
|
|
|
|
|
if (signal_pending(current))
|
|
|
|
ret = -ERESTARTSYS;
|
2006-10-04 23:26:14 +08:00
|
|
|
} while (!ret && !(status & (SPU_STATUS_STOPPED_BY_STOP |
|
2007-06-04 13:15:37 +08:00
|
|
|
SPU_STATUS_STOPPED_BY_HALT |
|
|
|
|
SPU_STATUS_SINGLE_STEP)));
|
2006-01-05 03:31:29 +08:00
|
|
|
|
2007-12-05 10:49:31 +08:00
|
|
|
spu_disable_spu(ctx);
|
2006-10-04 23:26:14 +08:00
|
|
|
ret = spu_run_fini(ctx, npc, &status);
|
2006-01-05 03:31:29 +08:00
|
|
|
spu_yield(ctx);
|
|
|
|
|
2008-02-08 12:50:41 +08:00
|
|
|
if ((status & SPU_STATUS_STOPPED_BY_STOP) &&
|
|
|
|
(((status >> SPU_STOP_STATUS_SHIFT) & 0x3f00) == 0x2100))
|
|
|
|
ctx->stats.libassist++;
|
|
|
|
|
2006-11-21 01:45:04 +08:00
|
|
|
if ((ret == 0) ||
|
|
|
|
((ret == -ERESTARTSYS) &&
|
|
|
|
((status & SPU_STATUS_STOPPED_BY_HALT) ||
|
2007-06-04 13:15:37 +08:00
|
|
|
(status & SPU_STATUS_SINGLE_STEP) ||
|
2006-11-21 01:45:04 +08:00
|
|
|
((status & SPU_STATUS_STOPPED_BY_STOP) &&
|
|
|
|
(status >> SPU_STOP_STATUS_SHIFT != 0x2104)))))
|
|
|
|
ret = status;
|
|
|
|
|
2007-06-04 13:15:37 +08:00
|
|
|
/* Note: we don't need to force_sig SIGTRAP on single-step
|
|
|
|
* since we have TIF_SINGLESTEP set, thus the kernel will do
|
|
|
|
* it upon return from the syscall anyawy
|
|
|
|
*/
|
2008-01-11 12:03:26 +08:00
|
|
|
if (unlikely(status & SPU_STATUS_SINGLE_STEP))
|
|
|
|
ret = -ERESTARTSYS;
|
|
|
|
|
|
|
|
else if (unlikely((status & SPU_STATUS_STOPPED_BY_STOP)
|
|
|
|
&& (status >> SPU_STOP_STATUS_SHIFT) == 0x3fff)) {
|
2006-11-28 02:18:53 +08:00
|
|
|
force_sig(SIGTRAP, current);
|
|
|
|
ret = -ERESTARTSYS;
|
2006-11-21 01:45:04 +08:00
|
|
|
}
|
|
|
|
|
2006-01-05 03:31:29 +08:00
|
|
|
out:
|
2006-10-04 23:26:14 +08:00
|
|
|
*event = ctx->event_return;
|
2007-12-20 15:39:59 +08:00
|
|
|
out_unlock:
|
2007-04-24 03:08:17 +08:00
|
|
|
mutex_unlock(&ctx->run_mutex);
|
2006-01-05 03:31:29 +08:00
|
|
|
return ret;
|
|
|
|
}
|