From: Gerd Hoffmann <kraxel@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] udev: add rules for qemu guests
Date: Tue, 25 Jan 2011 14:07:44 +0000 [thread overview]
Message-ID: <4D3ED930.9050608@redhat.com> (raw)
In-Reply-To: <1295952245-3038-1-git-send-email-kraxel@redhat.com>
On 01/25/11 14:39, Kay Sievers wrote:
> On Tue, Jan 25, 2011 at 11:44, Gerd Hoffmann<kraxel@redhat.com> wrote:
>> These patches enable usb autosuspend for the qemu emulated HID devices.
>> This reduces the cpu load for idle guests with a hid device attached
>> because the linux kernel will suspend the usb bus then and qemu can stop
>> running a 1000 Hz to emulate the (active) UHCI controller.
>
>> +dist_udevrules_DATA += extras/qemu/99-qemu-usb.rules
>
> The number should be 10-90 for the default things, or is there a
> dependency on anything else?
No dependency at all. What number do you suggest then?
>> +ACTION="add", SUBSYSTEM="usb", ATTR{product}="QEMU USB Mouse", ATTR{serial}="42", RUN+="qemu-usb-autosuspend %p"
>
> This should probably be a simple ATTR{power/control}="auto"
That should work indeed. Didn't know you can write sysfs files that way.
>> +path="$1"
>> +if test -f "/sys${path}/power/control"; then
>> + echo "auto"> "/sys${path}/power/control"
>> +elif test -f "/sys${path}/power/level"; then
>> + echo "auto"> "/sys${path}/power/level"
>> +fi
>
> Which one is the actual one? Is the second try only for older kernels?
Yes, it is for older kernels.
> That could go in the compat rules, udev does not ship rules for older
> kernels in the default installation.
Ok. Is there some way to express "power/control doesn't exist but
power/level does" as udev rule, so I can zap the shell script?
> Anyway, why isn't all this done in the kernel? Can't this be made
> working somehow?
As far I know the kernel doesn't do that by default because too much
broken hardware is out there which breaks when autosuspend is enabled by
default. I saw mentioned somewhere the plan is to have udev enable this
for known-good devices, so I'm trying that route :)
Havn't checked whenever there is a in-kernel white list for that stuff
which could be used instead.
cheers,
Gerd
next prev parent reply other threads:[~2011-01-25 14:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 10:44 [PATCH] udev: add rules for qemu guests Gerd Hoffmann
2011-01-25 12:01 ` Kay Sievers
2011-01-25 12:20 ` Gerd Hoffmann
2011-01-25 13:39 ` Kay Sievers
2011-01-25 14:07 ` Gerd Hoffmann [this message]
2011-01-25 14:21 ` Kay Sievers
2011-01-25 14:45 ` 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=4D3ED930.9050608@redhat.com \
--to=kraxel@redhat.com \
--cc=linux-hotplug@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).