All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Andi Kleen <andi@firstfloor.org>, Jiri Kosina <jkosina@suse.cz>,
	rjw@sisk.pl, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [regression] 2.6.30 leaking keys on console switch
Date: Fri, 23 Oct 2009 22:29:07 +0200	[thread overview]
Message-ID: <20091023202906.GD27185@elf.ucw.cz> (raw)
In-Reply-To: <20091021081529.GA1070@core.coreip.homeip.net>

On Wed 2009-10-21 01:15:30, Dmitry Torokhov wrote:
> On Mon, Oct 19, 2009 at 11:38:36PM +0200, Pavel Machek wrote:
> > On Wed 2009-10-14 00:39:28, Dmitry Torokhov wrote:
> > > On Wed, Oct 14, 2009 at 09:19:50AM +0200, Andi Kleen wrote:
> > > > > Btw, what kind of keyboard is this? I was playing today but I could not
> > > > > get my USB keyboards to report release of more than 1 key per report....
> > > > 
> > > > The log was with a PS/2<->USB adapter, with a PS/2 keyboard connected
> > > > to a USB port through it.
> > > > 
> > > 
> > > Hmm, I don't think I have one of those... It is curious beast - we have
> > > software autorepeat for HID but PS/2 keyboards do autorepeat
> > > themselves... What will combination do?
> > 
> > I always wondered how that's supposed to work... on loaded system. As
> > linux is not realtime system, it can't, afaict.
> 
> What exactly requires realtime? Surely not autorepeat...

Well, ps/2 does not provide timestamps, neither does USB AFAICT. So if
you hit say interrupt latency, you'll repeat keys one too many times
or something.

[But if X does autorepeat in software, that's even worse. That means
that scheduling latency can cause autorepeat glitches, and that's
probably what I'm seeing here. And I haaaaaaaaaaaaaaate when my
tyyyyyyping goes like this just because I have background load.]

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-10-23 20:29 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07  8:44 [regression] 2.6.30 leaking keys on console switch Andi Kleen
2009-07-07  8:50 ` Jiri Kosina
2009-07-07  9:12   ` Andi Kleen
2009-07-07  9:15     ` Jiri Kosina
2009-07-08  6:53   ` Dmitry Torokhov
2009-07-08 11:20     ` Jiri Kosina
2009-07-09 11:29       ` Jiri Kosina
2009-07-09 20:01         ` Andi Kleen
2009-10-14  4:58       ` Dmitry Torokhov
2009-10-14  7:19         ` Andi Kleen
2009-10-14  7:39           ` Dmitry Torokhov
2009-10-14  7:50             ` Dmitry Torokhov
2009-10-16  5:41             ` H. Peter Anvin
2009-10-19 21:38             ` Pavel Machek
2009-10-21  8:15               ` Dmitry Torokhov
2009-10-23 20:29                 ` Pavel Machek [this message]
2009-07-09 11:20     ` Jiri Kosina
2009-07-09 12:00       ` Andi Kleen
2009-07-09 20:03       ` Andi Kleen
2009-07-09 21:58         ` Jiri Kosina
2009-07-13  4:05       ` Dmitry Torokhov
2009-07-13  7:07         ` Jiri Kosina
2009-07-13  8:25           ` Andi Kleen
2009-07-16  9:02             ` Jiri Kosina
2009-07-16  9:24               ` Andi Kleen
2009-10-16  4:59                 ` Dmitry Torokhov

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=20091023202906.GD27185@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=andi@firstfloor.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.