From: Hannes Reinecke <hare@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: Delayed hotplug events
Date: Fri, 18 Jun 2004 08:12:33 +0000 [thread overview]
Message-ID: <40D2A3F1.9070100@suse.de> (raw)
In-Reply-To: <40D17ECC.20501@suse.de>
Oliver Neukum wrote:
> Am Freitag, 18. Juni 2004 01:57 schrieb Greg KH:
>
>>>On Thu, Jun 17, 2004 at 03:22:07PM -0500, linas@austin.ibm.com wrote:
>>>
>>>>By contrast, I can't see what's architecturally unclean about
>>>>having device drivers make the call as to when they think they
>>>>are finally up and ready to go, e.g. by making one puny subroutine
>>>>call at the end of thier init sequence. Why would this be a bad idea?
>>>
>>>Because it would be a major architecture change in the middle of a
>>>stable kernel series. I'm not going to agree to do that at this time.
>
>
> If you are willing to use a model of a blocking counter you can confine
> the changes to just the actual hotplug generation. The change is well
> encapsuled. Drivers not caring about the block/unblock affair simply get
> the old behavior.
> It's less elegant than waiting for the specific files, but workable.
>
You mean add an additional sysfs attribute which serves as an checkpoint
(i.e. if this attribute exists, the initialisation is done)?
Neat. Fixing the drivers (or even adding another generic function to
drivers/base/core.c) should be pretty straightforward.
One could even add another ENV which contains the name of the checkpoint
attribute; this way it's pretty clear to any script whether it needs to
wait or not.
This would also solve the timeout problem, as we could teach udevd to
wait for this checkpoint attribute to appear; if a matching 'remove'
event is received before the checkpoint is visible, udevd could just
drop both events.
Greg: acceptable?
Cheers,
Hannes
--
Dr. Hannes Reinecke hare@suse.de
SuSE Linux AG S390 & zSeries
Maxfeldstraße 5 +49 911 74053 688
90409 Nürnberg http://www.suse.de
-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
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:[~2004-06-18 8:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 11:21 Delayed hotplug events Hannes Reinecke
2004-06-17 18:09 ` Greg KH
2004-06-17 19:56 ` Oliver Neukum
2004-06-17 20:22 ` linas
2004-06-17 23:29 ` Patrick Mansfield
2004-06-17 23:39 ` Greg KH
2004-06-17 23:40 ` Greg KH
2004-06-17 23:57 ` Greg KH
2004-06-18 7:44 ` Oliver Neukum
2004-06-18 8:12 ` Hannes Reinecke [this message]
2004-06-18 8:47 ` Oliver Neukum
2004-06-18 9:32 ` Hannes Reinecke
2004-06-18 11:28 ` Oliver Neukum
2004-06-19 0:07 ` Greg KH
2004-06-19 8:16 ` Oliver Neukum
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=40D2A3F1.9070100@suse.de \
--to=hare@suse.de \
--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).