From: Alex Chiang <achiang@hp.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
pbadari@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-rc8-mm1 panic in rpaphp_register_slot()
Date: Sat, 19 Apr 2008 00:38:07 -0600 [thread overview]
Message-ID: <20080419063807.GB12987@ldl.fc.hp.com> (raw)
In-Reply-To: <1208384153.6958.302.camel@pasglop> <1208384185.6958.304.camel@pasglop>
Hi Ben,
* Benjamin Herrenschmidt <benh@kernel.crashing.org>:
>
> > The basic idea, which I keep botching on pSeries, is that when we
> > make a call to pci_hp_register, we now need to pass it:
> >
> > pci_hp_register(struct hotplug_slot *slot, struct pci_bus *bus, int slot_nr)
> >
> > I am having trouble figuring out the slot_nr argument. Basically,
> > I want to get the devfn of the slot we're looking at.
>
> I haven't looked in details yet, but I can already tell that things on
> pSeries aren't that simple because we don't necessarily know in advance
> about "slots"...
>
> When you add a physical PCI device to a partition, things can range from:
>
> - A device gets added to an existing bridge (ie. slot)
> - A whole P2P brigde gets added with that device below it (that's a slot too)
> - A whole PCI host bridge gets added with that device below it (or with
> a P2P bridge below it and the device below that).
>
> In the later case, it's hard to have any concept of slot since you don't
> know anything about the host bridge before it gets added to your partition :-)
>
> So I'm not sure how much we can use of your slot infrastructure, I'll have
> to look, I suspect it can cover some cases but not all of them.
*poke*
Any update on this?
Anything I can do to help?
> On Wed, 2008-04-16 at 13:03 -0700, Andrew Morton wrote:
> >
> > fwiw, http://userweb.kernel.org/~akpm/bh.gz (agains -rc9) contains all
> > of
> > -mm up to and including
> > pci-hotplug-acpi-pci-slot-detection-driver.patch
> > and is suitable for review/repair/etc.
>
> Ok, I'll use that.
Thanks,
/ac
next prev parent reply other threads:[~2008-04-19 6:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-04 17:53 Badari Pulavarty
2008-04-04 18:05 ` Alex Chiang
2008-04-04 20:19 ` Badari Pulavarty
2008-04-04 22:42 ` Alex Chiang
2008-04-04 23:35 ` Badari Pulavarty
2008-04-07 23:42 ` Alex Chiang
2008-04-16 0:36 ` Andrew Morton
2008-04-16 2:13 ` Alex Chiang
2008-04-16 3:08 ` Badari Pulavarty
2008-04-16 3:18 ` Alex Chiang
2008-04-16 3:20 ` Badari Pulavarty
2008-04-16 19:32 ` Badari Pulavarty
2008-04-16 19:59 ` Alex Chiang
2008-04-16 3:17 ` Alex Chiang
2008-04-16 7:45 ` Benjamin Herrenschmidt
2008-04-16 17:11 ` Alex Chiang
2008-04-16 20:03 ` Andrew Morton
2008-04-16 22:16 ` Benjamin Herrenschmidt
2008-04-16 22:15 ` Benjamin Herrenschmidt
2008-04-19 6:38 ` Alex Chiang [this message]
2008-04-19 7:03 ` Benjamin Herrenschmidt
2008-04-22 4:05 ` Alex Chiang
2008-04-22 5:07 ` Benjamin Herrenschmidt
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=20080419063807.GB12987@ldl.fc.hp.com \
--to=achiang@hp.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.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
all inboxes | Powered by JetHome®