From: Greg KH <greg@kroah.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@zip.com.au>,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Werner Almesberger <wa@almesberger.net>,
"Erik A. Hendriks" <hendriks@lanl.gov>
Subject: Re: [RFC] x86 ELF bootable kernels/Linux booting Linux/LinuxBIOS
Date: Thu, 31 Jan 2002 23:22:02 -0800 [thread overview]
Message-ID: <20020201072201.GA5666@kroah.com> (raw)
In-Reply-To: <m1zo2vb5rt.fsf@frodo.biederman.org> <8200.1012446189@kao2.melbourne.sgi.com>
In-Reply-To: <8200.1012446189@kao2.melbourne.sgi.com>
On Thu, Jan 31, 2002 at 02:03:09PM +1100, Keith Owens wrote:
> On 30 Jan 2002 19:42:14 -0700,
> ebiederm@xmission.com (Eric W. Biederman) wrote:
> >I like the other suggestion of extending the Hot-plug infrastructure.
> >In that case I just need to figure out how to logically Hot-unplug all
> >the devices in the system. That may be better than a
> >do_exitcalls()... As it automatically gets the discrimination right.
>
> In an ideal world, it should be enough to call the module_exit()
> functions in reverse order to the module_init(), LIFO. But check with
> the hotplug list, they have done most of the work on this problem.
Actually, no we haven't :)
We punt on the "do we remove the driver when the device disappears"
issue, and instead ignore the hotplug REMOVE events right now.
So far, no one's complained.
But to unplug all of the devices in the system in the proper order,
you're probably going to have to use the driverfs tree that is slowly
taking shape. That's the only representation of all physical devices in
the system that shows the topology correctly.
Hope this helps,
greg k-h
next prev parent reply other threads:[~2002-02-01 7:23 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-30 19:54 [RFC] x86 ELF bootable kernels/Linux booting Linux/LinuxBIOS Eric W. Biederman
2002-01-30 21:19 ` Andrew Morton
2002-01-30 23:52 ` Keith Owens
2002-01-31 2:42 ` Eric W. Biederman
2002-01-31 2:48 ` H. Peter Anvin
2002-01-31 4:27 ` Eric W. Biederman
2002-01-31 4:41 ` H. Peter Anvin
2002-01-31 5:15 ` Eric W. Biederman
2002-01-31 5:59 ` H. Peter Anvin
[not found] ` <m1n0yvaucy.fsf@frodo.biederman.org>
2002-01-31 17:57 ` H. Peter Anvin
2002-01-31 22:34 ` Eric W. Biederman
2002-01-31 22:52 ` H. Peter Anvin
2002-02-01 7:52 ` Eric W. Biederman
2002-01-31 17:35 ` Erik A. Hendriks
2002-01-31 23:36 ` Eric W. Biederman
2002-02-01 0:03 ` H. Peter Anvin
2002-02-01 9:03 ` Eric W. Biederman
2002-02-01 9:25 ` H. Peter Anvin
2002-02-01 15:42 ` Eric W. Biederman
2002-02-01 18:26 ` H. Peter Anvin
2002-02-02 16:17 ` Eric W. Biederman
2002-02-02 21:06 ` H. Peter Anvin
2002-02-02 23:02 ` Eric W. Biederman
2002-02-03 1:56 ` H. Peter Anvin
2002-02-03 18:43 ` Eric W. Biederman
2002-02-03 19:39 ` H. Peter Anvin
2002-02-03 22:18 ` Rob Landley
2002-02-03 22:24 ` H. Peter Anvin
2002-02-03 22:59 ` Rob Landley
2002-02-03 23:01 ` H. Peter Anvin
2002-02-03 23:47 ` Rob Landley
2002-02-04 1:34 ` H. Peter Anvin
2002-02-04 9:53 ` Marco Colombo
2002-02-04 16:19 ` H. Peter Anvin
2002-02-04 19:55 ` Eric W. Biederman
2002-02-04 20:51 ` Alan Cox
2002-02-04 20:40 ` H. Peter Anvin
2002-02-03 19:48 ` H. Peter Anvin
2002-02-04 20:16 ` Eric W. Biederman
2002-02-04 4:29 ` Keith Owens
2002-02-04 20:01 ` Eric W. Biederman
2002-02-04 12:49 ` Werner Almesberger
2002-02-04 16:26 ` H. Peter Anvin
2002-02-04 19:45 ` Eric W. Biederman
2002-02-04 21:02 ` Werner Almesberger
2002-02-04 21:08 ` H. Peter Anvin
2002-02-05 7:45 ` Eric W. Biederman
2002-02-01 0:46 ` Keith Owens
2002-01-31 3:03 ` Keith Owens
2002-02-01 7:22 ` Greg KH [this message]
2002-01-30 21:32 ` H. Peter Anvin
2002-01-31 2:31 ` Eric W. Biederman
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=20020201072201.GA5666@kroah.com \
--to=greg@kroah.com \
--cc=akpm@zip.com.au \
--cc=ebiederm@xmission.com \
--cc=hendriks@lanl.gov \
--cc=hpa@zytor.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wa@almesberger.net \
/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