From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: event sequencing
Date: Sat, 26 Feb 2005 14:00:24 +0000 [thread overview]
Message-ID: <1109426425.7400.74.camel@localhost.localdomain> (raw)
In-Reply-To: <9e473391050225081838f673c7@mail.gmail.com>
On Fri, 2005-02-25 at 11:18 -0500, Jon Smirl wrote:
>I working on adding hotplug monitor change detection code to some
>framebuffer drivers. I having trouble with event sequencing.
Oh, back to the original question and sorry for all that noise. :)
>In my probe function I do a class_simple_device_add() to create the
>class entry. Later in the probe function I do
>kobject_hotplug(&info->class_device->kobj, KOBJ_MOUNT); to indicate a
>monitor change.
>
>I'm receiving the MOUNT event before the ADD one. How can I control the order?
>
>Even in cases where MOUNT comes after ADD udev has not built my device
>nodes yet. My MOUNT app needs to use the device node. This is my
>bigger problem.
The event for the fb device needs to create a device node and therefore
takes longer than the mount event which seems to happen at the same
time. That's the reason for the unpredictable order, which can happen
anytime with "normal" hotplug.
But all events sent through the kobject_hotplug have kernel created
sequence numbers and udevd reorders the events to be executed in the
right order.
All events belonging to a device will be executed one after the other if
udevd recognizes a dependency, which is: the same devpath, a parent
device or a physical device behind it.
To solve all known kind of timing problems, we changed udev to be able
to take over the whole hotplug event and give the "normal" hotplug
scripts the same sane timing we need to have for udev to work properly.
udev versions later than 047 recognize if /proc/sys/kernel/hotplug is set
to /sbin/udevsend and then handle the hotplug scripts too.
> I'm using RH FC3 but this needs to work on all distributions when finished.
Fedora-Devel has already switched to "managed hotplug events" and the whole
system depends on udevd to handle hotplug.d/. Your should not see this
problem there.
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
next prev parent reply other threads:[~2005-02-26 14:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 16:18 event sequencing Jon Smirl
2005-02-25 16:53 ` Kay Sievers
2005-02-25 21:56 ` Jon Smirl
2005-02-26 0:16 ` Jon Smirl
2005-02-26 0:46 ` Kay Sievers
2005-02-26 1:18 ` Jon Smirl
2005-02-26 3:27 ` Greg KH
2005-02-26 3:29 ` Greg KH
2005-02-26 3:43 ` Kay Sievers
2005-02-26 3:58 ` Greg KH
2005-02-26 5:08 ` Kay Sievers
2005-02-26 5:35 ` Greg KH
2005-02-26 6:25 ` Jon Smirl
2005-02-26 13:11 ` Kay Sievers
2005-02-26 14:00 ` Kay Sievers [this message]
2005-02-26 17:34 ` Jon Smirl
2005-02-26 17:37 ` Jon Smirl
2005-02-26 18:28 ` Kay Sievers
2005-02-26 19:17 ` Jon Smirl
2005-02-26 19:41 ` Kay Sievers
2005-02-27 0:27 ` Jon Smirl
2005-02-28 4:53 ` Jon Smirl
2005-02-28 11:25 ` Kay Sievers
2005-02-28 19:07 ` Jon Smirl
2005-02-28 19:51 ` Greg KH
2005-02-28 19:52 ` Greg KH
2005-02-28 19:56 ` Greg KH
2005-02-28 21:13 ` Jon Smirl
2005-03-01 8:01 ` Greg KH
2005-03-01 8:30 ` Jon Smirl
2005-03-01 8:41 ` 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=1109426425.7400.74.camel@localhost.localdomain \
--to=kay.sievers@vrfy.org \
--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).