Re: split kobject creation and hotplug event generation

From: Greg KH (greg_at_kroah.com)
Date: 02/28/05

  • Next message: Valdis.Kletnieks_at_vt.edu: "2.6.11-rc4-mm1 - pcmcia weirdness/breakage"
    Date:	Mon, 28 Feb 2005 11:46:42 -0800
    To: Kay Sievers <kay.sievers@vrfy.org>
    
    

    On Sat, Feb 26, 2005 at 06:53:16AM +0100, Kay Sievers wrote:
    > This splits the implicit generation of a hotplug events from
    > kobject_add() and kobject_del(), to give the user of of these
    > functions control over the time the event is created.
    >
    > The kobject_register() and unregister functions still have the same
    > behavior and emit the events by themselves.
    >
    > The class, block and device core is changed now to emit the hotplug
    > event _after_ the "dev" file, the "device" symlink and the default
    > attributes are created. This will save udev from spinning in a stat() loop
    > to wait for the files to appear, which is expensive if we have a lot of
    > concurrent events.

    So, does this solve the issue that everyone has been complaining about
    for years with the hotplug event happening before the sysfs files are
    present? And if we add this, can we pretty much get rid of all of the
    wait_for_sysfs like logic in udev?

    thanks,

    greg k-h
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Valdis.Kletnieks_at_vt.edu: "2.6.11-rc4-mm1 - pcmcia weirdness/breakage"

    Relevant Pages

    • split kobject creation and hotplug event generation
      ... This splits the implicit generation of a hotplug events from ... functions control over the time the event is created. ... void kobject_unregister(struct kobject * kobj) ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: split kobject creation and hotplug event generation
      ... > This splits the implicit generation of a hotplug events from ... > functions control over the time the event is created. ... void kobject_unregister(struct kobject * kobj) ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: split kobject creation and hotplug event generation
      ... >> This splits the implicit generation of a hotplug events from ... >> functions control over the time the event is created. ... >> behavior and emit the events by themselves. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [linux-pm] Re: swsusp disk fails in bk-current - intel_agp at fault?
      ... > Or just avoid calling hotplug at all in resume case? ... > coldplug-like scan when userspace is ready... ... Can we just queue up hotplug events? ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: removable media revalidation - udev vs. devfs or static /dev
      ... >> I am even happy in a somewhat more general situation that you are. ... >> hotplug events so that udev can create the device nodes), ... > literally don't even have an easily read disk change signal, ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)