From: Paolo Bonzini <pbonzini@redhat.com>
To: Benjamin Herrenschmidt <benh@au1.ibm.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
li zhang <zhlcindy@gmail.com>,
qemu-devel@nongnu.org, zhlcindy@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [qemu-devel][RFC] Enable usb with default options
Date: Thu, 07 Jun 2012 10:49:56 +0200 [thread overview]
Message-ID: <4FD06B34.6060600@redhat.com> (raw)
In-Reply-To: <1339058438.24838.15.camel@pasglop>
Il 07/06/2012 10:40, Benjamin Herrenschmidt ha scritto:
> On Thu, 2012-06-07 at 10:32 +0200, Hans de Goede wrote:
>> Hi,
>>
>> Sorry for jumping in the middle of the thread, I missed the beginning
>> of this. Enabling USB by default, esp. emulating a USB mouse by default
>> is a *bad* idea. They way the periodic schedule of the various USB
>> controllers works means that emulating a USB device means a 1000 vm exits
>> per second extra, even when the vm is completely idle! USB powermanagement
>> can be used to negate this, but this is off in both Linux and Windows for
>> HID devices by default because there are too many broken HID devices.
>
> On the other hand it is the only choice of input device on some
> platforms such as pseries (and MacG5 when I get to make it work :-)
>
> Would it be possible to "whitelist" the QEMU emulated HID devices
> in the kernel to enable dynamic PM for them (at least when they sit
> alone on the bus) ? Or is our emulation busted too ?
At least in Fedora they are; from /usr/lib/udev/rules.d/42-usb-hid-pm.rules:
ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Mouse", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Tablet", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="usb", ATTR{product}=="QEMU USB Keyboard", ATTR{serial}=="42", TEST=="power/control", ATTR{power/control}="auto"
Paolo
next prev parent reply other threads:[~2012-06-07 8:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 9:48 [Qemu-devel] [qemu-devel][RFC] Enable usb with default options li zhang
2012-06-06 2:52 ` li zhang
2012-06-06 3:31 ` Benjamin Herrenschmidt
2012-06-06 5:42 ` Anthony Liguori
2012-06-06 6:03 ` li zhang
2012-06-06 21:13 ` Benjamin Herrenschmidt
2012-06-07 1:15 ` Anthony Liguori
2012-06-07 3:00 ` Benjamin Herrenschmidt
2012-06-07 3:03 ` Anthony Liguori
2012-06-07 4:52 ` li zhang
2012-06-07 4:39 ` li zhang
2012-06-07 4:43 ` Anthony Liguori
2012-06-07 4:53 ` li zhang
2012-06-07 8:07 ` Markus Armbruster
2012-06-07 9:19 ` Anthony Liguori
2012-06-07 10:05 ` Markus Armbruster
2012-06-07 11:51 ` Anthony Liguori
2012-06-12 8:06 ` Markus Armbruster
2012-06-07 8:32 ` Hans de Goede
2012-06-07 8:40 ` Benjamin Herrenschmidt
2012-06-07 8:49 ` Paolo Bonzini [this message]
2012-06-07 8:52 ` Hans de Goede
2012-06-07 9:05 ` Gerd Hoffmann
2012-06-07 9:17 ` Benjamin Herrenschmidt
2012-06-07 9:29 ` Li Zhang
2012-06-07 9:16 ` Benjamin Herrenschmidt
2012-06-07 9:50 ` Hans de Goede
2012-06-07 11:19 ` Benjamin Herrenschmidt
2012-06-07 11:35 ` Gerd Hoffmann
2012-06-07 8:54 ` Gerd Hoffmann
2012-06-06 22:14 ` Andreas Färber
-- strict thread matches above, loose matches on Subject: below --
2012-06-05 7:19 Li Zhang
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=4FD06B34.6060600@redhat.com \
--to=pbonzini@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=benh@au1.ibm.com \
--cc=hdegoede@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhlcindy@gmail.com \
--cc=zhlcindy@linux.vnet.ibm.com \
/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.