From: Paul Mackerras <paulus@samba.org>
To: linas <linas@austin.ibm.com>
Cc: linuxppc64-dev@ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] ppc64: EEH Avoid racing reports of errors
Date: Wed, 5 Oct 2005 21:23:11 +1000 [thread overview]
Message-ID: <17219.47007.44643.148022@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20050930010038.GF6173@austin.ibm.com>
Linas writes:
> 06-eeh-report-race.patch
> +/** Mark all devices that are peers of this device as failed.
> + * Mark the device driver too, so that it can see the failure
> + * immediately; this is critical, since some drivers poll
> + * status registers in interrupts ... If a driver is polling,
> + * and the slot is frozen, then the driver can deadlock in
> + * an interrupt context, which is bad.
> + */
> +
> +static inline void __eeh_mark_slot (struct device_node *dn)
> +{
> + while (dn) {
> + PCI_DN(dn)->eeh_mode |= EEH_MODE_ISOLATED;
> +
> + if (dn->child)
> + __eeh_mark_slot (dn->child);
> + dn = dn->sibling;
> + }
> +}
So this does the device node that we pass in, plus all the nodes that
come after it in its parent's list of children. On that basis I
expected you to pass in the first child of the EADS bridge, but I see:
> + pe_dn = find_device_pe (dn);
> + __eeh_mark_slot (pe_dn);
My understanding is that pe_dn will end up pointing to the device node
for the EADS bridge. Shouldn't you pass in pe_dn->child here, or
alternatively rearrange __eeh_mark_slot to do the node you give it
plus its children (recursively)?
Two other comments about __eeh_mark_slot: (1) despite the comment, the
function doesn't do anything to any pci_dev or pci_driver (not that it
should be touching any pci_driver), and (2) a recursive function can't
really be inline (unless gcc is smart enough to turn arbitrary
recursive functions into iterative functions, which I doubt :).
Regards,
Paul.
next prev parent reply other threads:[~2005-10-05 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 0:48 [PATCH 0/7] ppc64: Assorted minor EEH cleanups linas
2005-09-30 0:51 ` [PATCH 1/7] ppc64: EEH typos, include files, macros, whitespace linas
2005-10-05 11:11 ` Paul Mackerras
2005-10-07 19:46 ` linas
2005-09-30 0:53 ` [PATCH 2/7] ppc64: EEH PCI address cache cleanups linas
2005-09-30 0:54 ` [PATCH 3/7] ppc64: EEH Add event/internal state statistics linas
2005-10-05 11:14 ` Paul Mackerras
2005-10-07 14:59 ` linas
2005-09-30 0:56 ` [PATCH 4/7] ppc64: EEH PCI slot error details abstraction linas
2005-09-30 0:58 ` [PATCH 5/7] ppc64: EEH handle empty PCI slot failure linas
2005-09-30 1:00 ` [PATCH 6/7] ppc64: EEH Avoid racing reports of errors linas
2005-10-05 11:23 ` Paul Mackerras [this message]
2005-10-07 15:23 ` linas
2005-09-30 1:02 ` [PATCH 7/7] ppc64: EEH Halt if bad drivers spin in error condition linas
2005-09-30 4:49 ` Doug Maxey
2005-09-30 14:58 ` linas
2005-09-30 22:29 ` [PATCH 0/7] ppc64: Assorted minor EEH cleanups linas
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=17219.47007.44643.148022@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@ozlabs.org \
/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®