From: Daniel Axtens <dja@axtens.net>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH v2 3/8] powerpc/eeh: Force reset on fenced PHB
Date: Tue, 13 Oct 2015 16:18:19 +1100 [thread overview]
Message-ID: <87vbab2vok.fsf@gamma.ozlabs.ibm.com> (raw)
In-Reply-To: <20151013050151.GB28681@gwshan>
[-- Attachment #1: Type: text/plain, Size: 1977 bytes --]
Gavin Shan <gwshan@linux.vnet.ibm.com> writes:
> On Tue, Oct 13, 2015 at 12:43:23PM +1100, Daniel Axtens wrote:
>>Gavin Shan <gwshan@linux.vnet.ibm.com> writes:
>>
>>> + *
>>> + * When the PHB is fenced, we have to issue a reset to recover from
>>> + * the error. Override the result if necessary to have partially
>>> + * hotplug for this case.
>>> */
>>> pr_info("EEH: Notify device drivers to shutdown\n");
>>> eeh_pe_dev_traverse(pe, eeh_report_error, &result);
>>> + if ((pe->type & EEH_PE_PHB) &&
>>> + result != PCI_ERS_RESULT_NONE &&
>>> + result != PCI_ERS_RESULT_NEED_RESET)
>>> + result = PCI_ERS_RESULT_NEED_RESET;
>>I think we shouldn't discard the DISCONNECT state. A driver could ask
>>that the device be disconnected in the error_detected callback and we
>>should probably honour that.
>>
>
> Not exactly, the improvement is limited to fenced PHB, not frozen PE case.
> That's ok to discard DISCONNECT which forces all PHB's subordinate devices
> to offline permanently, which isn't so reasonable.
I see. That makes more sense now. It's still a bit hacky but I can see
why it should be the way it is.
Reviewed-by: Daniel Axtens <dja@axtens.net>
>
> This flag (DISCONNECT) has been there before the partial hotplug is
> added. I think the flag can die now with partial hotplug support.
OK. It looks like I need to put some more thought into partial hotplug.
I'm increasingly thinking it would be worth redesigning the state
machine and the enumerations/flags to better deal with how things have
evolved over the years.
Regards,
Daniel
>
> Thanks,
> Gavin
>
>>>
>>> /* Get the current PCI slot state. This can take a long time,
>>> * sometimes over 300 seconds for certain systems.
>>> --
>>> 2.1.0
>>>
>>> _______________________________________________
>>> Linuxppc-dev mailing list
>>> Linuxppc-dev@lists.ozlabs.org
>>> https://lists.ozlabs.org/listinfo/linuxppc-dev
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 859 bytes --]
next prev parent reply other threads:[~2015-10-13 5:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 3:58 [PATCH v2 0/8] EEH Improvement and Cleanup Gavin Shan
2015-10-08 3:58 ` [PATCH v2 1/8] powerpc/eeh: Don't unfreeze PHB PE after reset Gavin Shan
2015-10-21 11:41 ` [v2,1/8] " Michael Ellerman
2015-10-08 3:58 ` [PATCH v2 2/8] powerpc/eeh: More relexed hotplug criterion Gavin Shan
2015-10-12 22:55 ` Daniel Axtens
2015-10-12 23:25 ` Gavin Shan
2015-10-13 2:48 ` Daniel Axtens
2015-10-13 4:28 ` Gavin Shan
2015-10-13 23:48 ` Daniel Axtens
2015-10-14 1:33 ` Gavin Shan
2015-10-08 3:58 ` [PATCH v2 3/8] powerpc/eeh: Force reset on fenced PHB Gavin Shan
2015-10-13 1:43 ` Daniel Axtens
2015-10-13 5:01 ` Gavin Shan
2015-10-13 5:18 ` Daniel Axtens [this message]
2015-10-08 3:58 ` [PATCH v2 4/8] powerpc/eeh: More relxed condition for enabled IO path Gavin Shan
2015-10-08 3:58 ` [PATCH v2 5/8] powerpc/pseries: Cleanup on pseries_eeh_get_state() Gavin Shan
2015-10-08 4:15 ` Andrew Donnellan
2015-10-08 3:58 ` [PATCH v2 6/8] powerpc/powernv: Cleanup on EEH comments Gavin Shan
2015-10-08 3:58 ` [PATCH v2 7/8] powerpc/powernv: Remove pnv_eeh_cap_start() Gavin Shan
2015-10-08 4:18 ` Andrew Donnellan
2015-10-08 3:58 ` [PATCH v2 8/8] powerpc/powernv: Simplify pnv_eeh_set_option() Gavin Shan
2015-10-08 4:33 ` Andrew Donnellan
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=87vbab2vok.fsf@gamma.ozlabs.ibm.com \
--to=dja@axtens.net \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linuxppc-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;
as well as URLs for NNTP newsgroup(s).