From: Kay Sievers <kay.sievers@vrfy.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: Greg KH <greg@kroah.com>, Adrian Bunk <bunk@stusta.de>,
Andrew Morton <akpm@osdl.org>,
rml@novell.com, linux-kernel@vger.kernel.org, "Brown,
Len" <len.brown@intel.com>,
acpi-devel@lists.sourceforge.net, rusty@rustycorp.com.au
Subject: Re: 2.6.10-rc1-mm3: ACPI problem due to un-exported hotplug_path
Date: Fri, 5 Nov 2004 21:45:39 +0100 [thread overview]
Message-ID: <20041105204539.GA24175@vrfy.org> (raw)
In-Reply-To: <20041105123254.A17224@unix-os.sc.intel.com>
On Fri, Nov 05, 2004 at 12:32:56PM -0800, Ashok Raj wrote:
> On Fri, Nov 05, 2004 at 12:10:12PM -0800, Kay Sievers wrote:
> >
> > On Fri, Nov 05, 2004 at 10:05:13AM -0800, Greg KH wrote:
> > > > The following error (compin from Linus' tree) is caused by the
> > fact that
> > > > hotplug_path is no longer EXPORT_SYMBOL'ed:
> > > >
> > > >
> > > > <-- snip -->
> > > >
> > > > if [ -r System.map ]; then /sbin/depmod -ae -F System.map
> > 2.6.10-rc1-mm3; fi
> >
> > I've found it. This wants to introduce a new direct /sbin/hotplug
> > call,
> > with "add" and "remove" events, without sysfs support.
> >
> > It should use class support or kobject_hotplug() instead. Nobody
> > should
> > fake hotplug events anymore, cause every other notification transport
> > will not get called (currently uevent over netlink).
> >
>
> we were discussing this exact thing recently.. we maybe able to clean this up.. here is why
> we are doing this manual thingy...
>
> When we support physical component hotplug, we want to create the sysfs entries, but that doesnt
> mean the component (i.e CPU or memory) is hotplugged. The reason is for node level hotplug
> there are sequencing requirements, memory needs to be brought up first before cpu, and also
> the error handling/policy requirments which we want the user space to handle it and not from
> kernel side.
>
>
> the sequence is when physical arrival of cpu is seen, we will just create a sysfs entry
> which will also send an add event (which really is just cpu arrival, and sysfs created).
>
> In our model the event is just consumed by the script cpu.agent, which would in turn decide and
> bring the cpu up by
>
> #echo 1> /sys/devices/system/cpu/cpu#/online
>
> what apps really would care about is the ONLINE (which doesnt exist) event itself, and the
> OFFLINE. The ADD/REMOVE only indicate sysfs entries appear and disappear.
>
> I dont know if adding ONLINE/OFFLINE is the right thing, or use the CHANGE notification
> to inform.
>
> This is an area that needs more though which is slightly different from how other devices are being handled.
There is already an "offline" event used for cpu's in drivers/base/cpu.c.
It was recently converted from calling /sbin/hotplug directly :)
ChangeSet: 1.2021
http://linus.bkbits.net:8080/linux-2.5/patch@1.2021?nav=index.html|src/|src/kernel|related/kernel/cpu.c|cset@1.2021
Kay
next prev parent reply other threads:[~2004-11-05 20:47 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-05 8:13 2.6.10-rc1-mm3 Andrew Morton
2004-11-05 9:41 ` 2.6.10-rc1-mm3 Lorenzo Allegrucci
2004-11-05 10:17 ` 2.6.10-rc1-mm3 Andrew Morton
2004-11-05 10:48 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:36 ` 2.6.10-rc1-mm3 Lorenzo Allegrucci
2004-11-05 10:22 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 10:38 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 11:09 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 11:17 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 11:24 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 11:43 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:15 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 12:22 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:57 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 13:02 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 17:47 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 11:20 ` 2.6.10-rc1-mm3 Russell King
2004-11-05 11:30 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 10:17 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 15:54 ` 2.6.10-rc1-mm3 Michael Baehr
2004-11-05 10:56 ` 2.6.10-rc1-mm3 Con Kolivas
2004-11-05 16:45 ` 2.6.10-rc1-mm3: ACPI problem due to un-exported hotplug_path Adrian Bunk
2004-11-05 18:05 ` Greg KH
2004-11-05 20:10 ` Kay Sievers
2004-11-05 20:32 ` Ashok Raj
2004-11-05 20:43 ` Greg KH
2004-11-05 20:45 ` Kay Sievers [this message]
2004-11-05 20:42 ` Greg KH
2004-11-06 5:18 ` Keshavamurthy Anil S
2004-11-06 5:50 ` Dmitry Torokhov
2004-11-09 22:55 ` Greg KH
2004-11-09 23:48 ` [ACPI] " Dmitry Torokhov
2004-11-10 0:08 ` Greg KH
2004-11-10 4:15 ` Dmitry Torokhov
2004-11-16 5:54 ` Greg KH
2004-11-05 16:52 ` 2.6.10-rc1-mm3: drm_ati_pcigart_{init,cleanup} multiple definition Adrian Bunk
2004-11-05 17:19 ` Dave Airlie
2004-11-05 17:33 ` Jon Smirl
2004-11-05 18:07 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 18:48 ` 2.6.10-rc1-mm3: (fix for make xconfig) Rafael J. Wysocki
2004-11-05 20:26 ` Sam Ravnborg
2004-11-08 22:34 ` Sam Ravnborg
2004-11-05 18:07 ` 2.6.10-rc1-mm3 Adam Heath
2004-11-06 7:16 ` 2.6.10-rc1-mm3 Pasi Savolainen
2004-11-06 9:39 ` [PATCH][TRIVIAL] sched.c whitespace mangler Con Kolivas
2004-11-07 1:32 ` 2.6.10-rc1-mm3: "bttv card=" breakage Adrian Bunk
2004-11-07 2:15 ` Andrew Morton
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=20041105204539.GA24175@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=ashok.raj@intel.com \
--cc=bunk@stusta.de \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@novell.com \
--cc=rusty@rustycorp.com.au \
/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