public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@insightbb.com>
To: Dave Neuer <mr.fred.smoothie@pobox.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Vojtech Pavlik <vojtech@suse.cz>
Subject: Re: [RFT/PATCH] i8042: remove polling timer (v6)
Date: Sun, 29 Oct 2006 22:34:00 -0500	[thread overview]
Message-ID: <200610292234.02487.dtor@insightbb.com> (raw)
In-Reply-To: <161717d50610291520i5076901blf8bf253eba6148cc@mail.gmail.com>

On Sunday 29 October 2006 18:20, Dave Neuer wrote:
> On 8/23/06, Dmitry Torokhov <dtor@insightbb.com> wrote:
> > Hi everyone,
> >
> > Here is another version of the patch removing polling timer from i8042
> > which is needed if we want tickless kernel. Keyboards should now work
> > on boxes that do not have mouse plugged in. PLease give it a test.
> 
>  What's the intent of this; just to allow tickless? Or is it also to
> make the i8042 driver less racy? I ask because I've applied this over
> (a modified) 2.6.18 on my Compaq Presario X1010us laptop which has
> been driving me crazy w/ Synaptics problems and keyboard problems
> (intermittent, but   frequent enough lately that I finally figured I
> needed to do something about it).
> 
> If removing raciness is part of the goal, isn't the window in
> i8042_aux_write still a problem?
> 
> 	if (port->mux == -1)
> 		retval = i8042_command(&c, I8042_CMD_AUX_SEND);
> 	else
> 		retval = i8042_command(&c, I8042_CMD_MUX_SEND + port->mux);
> 
>         /* i8042_command has re-enabled interrupts;
>            what happens if real interrupt happens here, before we call
> the ISR ourselves? */
> 
> 	i8042_interrupt(0, NULL, NULL);
> 	return retval;
> }
>

Hi Dave,

i8042_interrupt() uses spinlock to serialize access to the KBC so if real
interrupt happens before we call i8042_interrupt() manually (and it should
normally happen) it will just process the response and second i8042_interrupt()
will be just a no-op.

Sorry, freel like crap, will try re-reading and responding to the rest of
your email later...
 
-- 
Dmitry

  reply	other threads:[~2006-10-30  3:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-24  3:11 [RFT/PATCH] i8042: remove polling timer (v6) Dmitry Torokhov
2006-10-29 23:20 ` Dave Neuer
2006-10-30  3:34   ` Dmitry Torokhov [this message]
2006-10-30  9:08     ` Vojtech Pavlik
2006-10-30 13:01       ` Dave Neuer
2006-10-30 14:22         ` Dave Neuer
2006-11-03  5:56           ` Dmitry Torokhov
2006-11-03  8:18             ` Vojtech Pavlik
2006-11-03 14:08               ` Dmitry Torokhov
2006-11-03  6:03   ` Dmitry Torokhov
2006-11-06 16:22     ` Dave Neuer
2006-11-06 16:48       ` Dmitry Torokhov
2006-11-06 17:09         ` Dave Neuer
2006-11-06 17:21         ` Dave Neuer
2006-11-20  4:36         ` Dave Neuer
2006-11-20  5:04       ` Dave Neuer

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=200610292234.02487.dtor@insightbb.com \
    --to=dtor@insightbb.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mr.fred.smoothie@pobox.com \
    --cc=vojtech@suse.cz \
    /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