All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] udev 42-qemu-usb.rules considered harmful?
Date: Wed, 17 Oct 2012 12:41:22 +0400	[thread overview]
Message-ID: <507E6F32.4070009@msgid.tls.msk.ru> (raw)

Hello.

I noticed that "some" versions of linux guests shows quite
bad behavour of mouse cursor: it freezes after some idle
time, and when you move mouse, it jumps after some delay
to rather distant position.  So, mouse becomes "freezy/jumpy",
so to say.

Quite some painful debugging pointed to the following
udev rule:

---- /lib/udev/rules.d/42-qemu-usb.rules ----
#
# Enable autosuspend for qemu emulated usb hid devices.
#
# Note that there are buggy qemu versions which advertise remote
# wakeup support but don't actually implement it correctly.  This
# is the reason why we need a match for the serial number here.
# The serial number "42" is used to tag the implementations where
# remote wakeup is working.
#
ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Tablet", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"
---- end ----

(And a few other similar rules, for other QEMU USB devices).

Removing this rule restores correct mouse behavour.

As far as I can see, this rule is to reduce polling interrupt
frequency, but apparently it does not help: any usb device
connected to guest, and the host CPU usage rises anyway, with
or without this rule.

Now the question: should we remove this rule?  Why it is needed
to start with?

(qemu version 1.1, but the same bad behavour happens with other
versions too).

Thanks,

/mjt

             reply	other threads:[~2012-10-17  8:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-17  8:41 Michael Tokarev [this message]
2012-10-17  8:56 ` [Qemu-devel] udev 42-qemu-usb.rules considered harmful? Gerd Hoffmann
2012-10-17  9:15   ` Michael Tokarev
2012-10-17  9:21     ` Michael Tokarev
2012-10-17 10:58     ` Gerd Hoffmann

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=507E6F32.4070009@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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.