From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linas Vepstas <linas@austin.ibm.com>
Cc: linux-kernel@vger.kernel.org,
long <tlnguyen@snoqualmie.dp.intel.com>,
Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
Greg KH <greg@kroah.com>,
ak@muc.de, Paul Mackerras <paulus@samba.org>,
linuxppc64-dev <linuxppc64-dev@ozlabs.org>,
linux-pci@atrey.karlin.mff.cuni.cz, johnrose@us.ibm.com
Subject: Re: [PATCH 8/13]: PCI Err: Event delivery utility
Date: Wed, 29 Jun 2005 11:59:47 +1000 [thread overview]
Message-ID: <1120010387.5133.235.camel@gaston> (raw)
In-Reply-To: <20050628235932.GA6429@austin.ibm.com>
On Tue, 2005-06-28 at 18:59 -0500, Linas Vepstas wrote:
> pci-err-8-pci-err-event.patch
>
> [RFC]
>
> PCI Error distribution utility routine. This patch defines
> a utility routine that hasn't yet been discussed much on
> the mailing list; I've made this architecture independent
> with the idea that various architectures may find it handy,
> but its not directly required, or relevant, to the overall
> EEH error recovery mechanism. (It could be buried in
> arch-dependent code or implemented differently.)
>
> The current design has the arch dependent code detect
> a PCI bus error. That code uses this utility to generate
> a detection event. This event is then caught by PCI
> hotplug code, which drives the slot recovery. If the
> affected device drivers have recovery callbacks, these
> are used; all other devices are hotplugged.
>
> There are certainly other (simpler) ways to attach the
> arch-specific error detection code to the hot-plug mediated
> recovery code; this routine is rather left-over from
> earlier email discussions. Should this stay, or not?
Certainly needs to be in a separate .h at least ... Also, you have some
lifetime issues. You probably want to do a get() on pci_dev when you put
it in your struct and put() it after the notifier... Oh wait, you are
doing pci_dev_put() ... but no pci_dev_get() ... The later must be
missing from peh_send_failure_event().
I'd keep that in arch code for now.
Ben.
next prev parent reply other threads:[~2005-06-29 2:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 23:59 [PATCH 8/13]: PCI Err: Event delivery utility Linas Vepstas
2005-06-29 1:59 ` Benjamin Herrenschmidt [this message]
2005-06-29 21:14 ` Linas Vepstas
2005-06-29 23:42 ` Benjamin Herrenschmidt
2005-06-30 0:29 ` Linas Vepstas
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=1120010387.5133.235.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=ak@muc.de \
--cc=greg@kroah.com \
--cc=johnrose@us.ibm.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linuxppc64-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=seto.hidetoshi@jp.fujitsu.com \
--cc=tlnguyen@snoqualmie.dp.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.