linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Olivier Blin <oblin@mandriva.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [RFC] coldplug - emit hotplug events from sysfs
Date: Mon, 03 Oct 2005 13:00:40 +0000	[thread overview]
Message-ID: <m3k6guu553.fsf@mandriva.com> (raw)
In-Reply-To: <20051001124943.GA26076@vrfy.org>

Kay Sievers <kay.sievers@vrfy.org> writes:

>> It looks really nice, but will we still be able to differientate
>> coldplug events in udev rules?
>> For example, in Mandriva, we do PCI coldplug for USB controllers only,
>> because we handle other stuff (sound, network, ...) later in
>> services. We used to rely on UDEV_START in udev rules.
>
> Not with this simple patch. It would be possible by adding an additional
> parameter to kobject_hotplug() to add an aditional key. Or we could use a
> different ACTION value and map it with udev...
>
> But unlike udevstart/udevsynthesize, you have complete control which
> events are generated, cause you will do it from a shell script and not
> with a binary. Wouldn't it work, to just trigger the events for the
> usb controllers and and leave the others alone?

Actually, we also need to know the class of the pci device, that's why
it was handy to use an udev rule.
But of course, we could use something like that:
for i in /sys/bus/pci/devices/*; do egrep -q '0x0c03[012]0' $i/class && echo 1 > $i/uevent; done

> To play with it, I use this stupid hack in an early init-script and
> it works without udevstart or any other coldplug logic.
> After mounting tmpfs, creating /dev/null, disabling /sbin/hotplug and
> starting udevd, it creates the tty devices, waits for the events to
> finish, then sends out all remaining events to finish asynchronously:

Thanks for the explanation

> Anyway, it works on two of my boxes and is the fastest udev/coldplug
> bootup, I've ever seen. :)

Strange it's that better, udevstart/synthetize only browsed the
sysfs directories and added some environment variables.
Browsing with bash should be almost as slow.

-- 
Olivier Blin
Mandriva



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-10-03 13:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 12:49 [RFC] coldplug - emit hotplug events from sysfs Kay Sievers
2005-10-03 10:03 ` Scott James Remnant
2005-10-03 10:29 ` Olivier Blin
2005-10-03 12:21 ` Kay Sievers
2005-10-03 13:00 ` Olivier Blin [this message]
2005-10-03 15:21 ` Scott James Remnant
2005-10-03 15:29 ` Kay Sievers
2005-10-03 16:22 ` Greg KH
2005-10-03 16:31 ` Scott James Remnant
2005-10-03 17:44 ` Olivier Blin
2005-10-03 17:49 ` Bill Nottingham
2005-10-03 17:59 ` Olivier Blin
2005-10-04 21:00 ` Greg KH
2005-10-28 20:12 ` Scott James Remnant
2005-10-28 20:14 ` Greg KH
2005-10-29  2:29 ` Alexander E. Patrakov
2005-10-29  2:43 ` Greg KH

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=m3k6guu553.fsf@mandriva.com \
    --to=oblin@mandriva.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).