From: Arnd Bergmann <arnd@arndb.de>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org,
Al Viro <viro@ftp.linux.org.uk>, Mark Nutter <mnutter@us.ibm.com>
Subject: [PATCH 00/13] spufs fixes and cleanups
Date: Wed, 04 Jan 2006 20:31:20 +0100 [thread overview]
Message-ID: <20060104193120.050539000@localhost> (raw)
In a review almost a month ago, Al Viro found numerous
problems in the current spufs code. I now finally found
some time to go through those and attempt to fix them.
There are also a few other changes in this series that
should also help, in particular improved interrupt
sending and an abstraction for priviledged register
access (as suggested by Masato Noguchi and Geoff Levand).
Please apply to powerpc.git before sending spufs upstream.
Al, could you have a look over this to see if it addresses
all the concerns you had and if I broke it in new ways?
Arnd <><
arch/powerpc/platforms/cell/Makefile | 5
arch/powerpc/platforms/cell/interrupt.c | 42 ++--
arch/powerpc/platforms/cell/interrupt.h | 1
arch/powerpc/platforms/cell/spu_base.c | 67 +++----
arch/powerpc/platforms/cell/spu_priv1.c | 133 ++++++++++++++
arch/powerpc/platforms/cell/spufs/Makefile | 2
arch/powerpc/platforms/cell/spufs/file.c | 167 +----------------
arch/powerpc/platforms/cell/spufs/hw_ops.c | 19 --
arch/powerpc/platforms/cell/spufs/inode.c | 156 ++++++++-------
arch/powerpc/platforms/cell/spufs/run.c | 131 ++++++++++++++
arch/powerpc/platforms/cell/spufs/sched.c | 13 +
arch/powerpc/platforms/cell/spufs/spufs.h | 35 +++
arch/powerpc/platforms/cell/spufs/switch.c | 139 +++++----------
arch/powerpc/platforms/cell/spufs/syscalls.c | 5
arch/powerpc/platforms/cell/spufs/context.c | 11 -
include/asm-powerpc/spu.h | 42 +++-
20 files changed, 565 insertions(+), 407 deletions(-)
next reply other threads:[~2006-01-04 19:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 19:31 Arnd Bergmann [this message]
2006-01-04 19:31 ` [PATCH 01/13] spufs: fix locking in spu_acquire_runnable Arnd Bergmann
2006-01-04 19:31 ` [PATCH 02/13] spufs: dont hold root->isem in spu_forget Arnd Bergmann
2006-01-04 19:31 ` [PATCH 03/13] spufs: check for proper file pointer in sys_spu_run Arnd Bergmann
2006-01-04 19:31 ` [PATCH 04/13] spufs: serialize sys_spu_run per spu Arnd Bergmann
2006-01-04 19:31 ` [PATCH 05/13] spufs fix spu_acquire_runnable error path Arnd Bergmann
2006-01-04 19:31 ` [PATCH 06/13] spufs: dont leak directories in failed spu_create Arnd Bergmann
2006-01-04 19:31 ` [PATCH 07/13] spufs: fix spufs_fill_dir error path Arnd Bergmann
2006-01-04 19:31 ` [PATCH 08/13] spufs: clean up use of bitops Arnd Bergmann
2006-01-04 19:31 ` [PATCH 09/13] spufs: move spu_run call to its own file Arnd Bergmann
2006-01-04 19:31 ` [PATCH 10/13] spufs: abstract priv1 register access Arnd Bergmann
2006-01-04 19:31 ` [PATCH 11/13] spufs: fix sparse warnings Arnd Bergmann
2006-01-04 19:31 ` [PATCH 12/13] spufs: fix allocation on 64k pages Arnd Bergmann
2006-01-04 19:31 ` [PATCH 13/13] spufs: set irq affinity for running threads Arnd Bergmann
2006-01-05 4:42 ` Nathan Lynch
2006-01-05 14:05 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060104193120.050539000@localhost \
--to=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
--cc=mnutter@us.ibm.com \
--cc=paulus@samba.org \
--cc=viro@ftp.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox