[PATCH 3/3] xfree86: Add a conservative SIGIO handler path

[Keith Packard]

On Thu, 14 Oct 2010 16:26:07 -0300, Tiago Vignatti <tiago.vignatti at nokia.com> wrote:
> On Thu, Oct 14, 2010 at 06:49:06PM +0200, ext Adam Jackson wrote:
> > Instead of actually processing input in the handler, the conservative
> > path just raises enough of a dispatch exception to bomb out of request
> > processing and handle input instead.
> 
> ajax, I understand the rationale but would be great if you elaborate a bit
> defending why we need _another_ method here. We're adding more complexity and,
> for instance, we would have to justify the removal of this new method when
> introducing the input-thread given I was already assuming like dead all SIGIO
> paths.

I don't think he's proposing that we add another path here. We will end
up with two ways of reading input events:

 1) separate input thread reads input data
 2) input data read at the beginning of ProcessInputEvents

All that the SIGIO change does is ensure that ProcessInputEvents gets
called as soon as possible when input is available. Without this, the
sprite will be stuck on the screen when the X server is busy processing
requests.

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20101020/15d1bbff/attachment.pgp>