Date: Sun, 15 May 2005 11:07:05 +0200
From: Pavel Machek <pavel@ucw.cz>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linuxppc64-dev@ozlabs.org,
       linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
       Anton Blanchard <anton@samba.org>
Subject: Re: [PATCH 7/8] ppc64: SPU file system
Message-ID: <20050515090705.GA2343@elf.ucw.cz>
References: <200505132117.37461.arnd@arndb.de> <200505132129.07603.arnd@arndb.de> <1116027079.5128.32.camel@gaston>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1116027079.5128.32.camel@gaston>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1037
Lines: 26

Hi!

> > /run	A stub file that lets us do ioctl. The only ioctl
> > 	method we need is the spu_run() call. spu_run suspends
> > 	the current thread from the host CPU and transfers
> > 	the flow of execution to the SPU.
> > 	The ioctl call return to the calling thread when a state
> > 	is entered that can not be handled by the kernel, e.g.
> > 	an error in the SPU code or an exit() from it.
> > 	When a signal is pending for the host CPU thread, the
> > 	ioctl is interrupted and the SPU stopped in order to
> > 	call the signal handler.
> 
> ioctl's are generally considered evil ... what about a write() method
> writing a command ?

That's even more evil than ioctl()... Try doing 32-vs-64bit conversion
on write...
								Pavel
-- 
Boycott Kodak -- for their patent abuse against Java.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/