From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
Greg KH <greg@kroah.com>,
ink@jurassic.park.msu.ru, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH] Make hot unplugging of PCI buses work
Date: Sun, 23 Feb 2003 19:32:29 +0000 [thread overview]
Message-ID: <20030223193229.F20405@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0302231054420.11584-100000@home.transmeta.com>; from torvalds@transmeta.com on Sun, Feb 23, 2003 at 10:57:10AM -0800
On Sun, Feb 23, 2003 at 10:57:10AM -0800, Linus Torvalds wrote:
> On Sun, 23 Feb 2003, Russell King wrote:
> > Linus - this patch is for discussion, NOT for applying unless you have
> > zero problems with it since it actively breaks existing hotplug PCI.
>
> Well, I definitely want it, and you should add Alan to the cc list since
> he apparently even _has_ one of these devices.
Alan kindly sent one of these beasts to me, which renewed my interest
in this area. I'll forward stuff so far.
> > Furthermore, I propose that pci_remove_device() shall disappear -
> > and this devices makes it so (thereby breaking existing hotplug
> > drivers.)
>
> Can't you just fix up the current users to use "pci_remove_bus_device()".
> The breakage seems a bit spiteful ;)
I'd like to hear Gregs comments first - Greg knows the hotplugging code
better than me. It appears to have its own way of decending some of the
PCI buses, but it seems unclear why it needs to supervise removal of
devices which are downstream from the hotplug slot.
As far as inserting this device, there needs to be a fair number of other
to the PCI layer to make stuff work sanely. Currently, in order, we:
1. discovering all devices
2. once all devices have been initialised, registering each
device with sysfs and thereby letting the drivers know.
3. apply any fixups needed
4. initialise any resources that need initialising
The drivers quite rightfully moan, and it isn't a pretty sight.
IMO, what we should be doing, in order, is:
1. discovering all devices
2. apply any fixups needed
3. initialise any resources that need initialising
4. once all devices have been initialised, registering each
device with sysfs and thereby letting the drivers know.
We need to wait until everything is setup for step 4 because we may
(and do in the case of this split-bridge) need to program PCI-PCI
bridges before the devices become accessible.
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-02-23 19:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-23 17:34 [PATCH] Make hot unplugging of PCI buses work Russell King
2003-02-23 18:16 ` Jeff Garzik
2003-02-23 18:57 ` Linus Torvalds
2003-02-23 19:32 ` Russell King [this message]
2003-02-23 21:29 ` Alan Cox
2003-02-24 0:10 ` Ivan Kokshaysky
2003-02-23 21:01 ` Scott Murray
2003-02-23 21:24 ` Russell King
2003-02-23 22:27 ` Scott Murray
2003-02-24 0:59 ` Linus Torvalds
2003-02-24 5:40 ` Scott Murray
2003-02-24 6:08 ` Greg KH
2003-02-24 5:48 ` Greg KH
2003-02-24 10:03 ` Russell King
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=20030223193229.F20405@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=ink@jurassic.park.msu.ru \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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