From: "Guilherme G. Piccoli" <gpiccoli@linux.vnet.ibm.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>,
"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2] powerpc/powernv: Add pci_reset_phbs parameter to issue a PHB reset
Date: Wed, 6 Dec 2017 17:28:39 -0200 [thread overview]
Message-ID: <c756e923-791e-154e-cdcb-50cb6bd06dd7@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAKTCnz=JLBGDF7O9saMiGNC4jUsHDpp1A3oRk+7TDfn5st_CKA@mail.gmail.com>
On 11/21/2017 12:35 AM, Balbir Singh wrote:
> On Thu, Nov 16, 2017 at 11:14 PM, Guilherme G. Piccoli
> <gpiccoli@linux.vnet.ibm.com> wrote:
>> On 11/16/2017 01:49 AM, Balbir Singh wrote:
>>> On Thu, Oct 26, 2017 at 2:27 AM, Guilherme G. Piccoli
>>> <gpiccoli@linux.vnet.ibm.com> wrote:
>>>> During a kdump kernel boot in PowerPC, we request a reset of the PHBs
>>>> to the FW. It makes sense, since if we are booting a kdump kernel it
>>>> means we had some trouble before and we cannot rely in the adapters'
>>>> health; they could be in a bad state, hence the reset is needed.
>>>>
>>>> But this reset is useful not only in kdump - there are situations,
>>>> specially when debugging drivers, that we could break an adapter in
>>>> a way it requires such reset. One can tell to just go ahead and
>>>> reboot the machine, but happens that many times doing kexec is much
>>>> faster, and so preferable than a full power cycle.
>>>>
>>>> This patch adds the pci_reset_phbs parameter to perform such reset
>>>> when desired by the user.
>>>>
>>>
>>> Do we care to reset specific phbs or all of them? I guess all based on
>>> your description.
>>
>> Exactly Balbir, it does reset all of them. We could add such
>> granularity, but I don't see much usability..
>> But if somebody feels it's useful, we can change...
>>
>
> OK.. makes sense, any reason why this can't be folded into reset_devices?
> I guess we want reset_phbs to be independent of reset_devices
It was, in v1. But mpe asked it to be a powerpc specific parameter heheh
Cheers,
Guilherme
>
> Balbir
>
next prev parent reply other threads:[~2017-12-06 19:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 15:27 [PATCH v2] powerpc/powernv: Add pci_reset_phbs parameter to issue a PHB reset Guilherme G. Piccoli
2017-11-09 21:33 ` Guilherme G. Piccoli
2017-11-13 4:25 ` Michael Ellerman
2017-11-16 3:49 ` Balbir Singh
2017-11-16 12:14 ` Guilherme G. Piccoli
2017-11-21 2:35 ` Balbir Singh
2017-12-06 19:28 ` Guilherme G. Piccoli [this message]
2017-12-08 12:03 ` Michael Ellerman
2017-12-08 18:43 ` Guilherme G. Piccoli
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=c756e923-791e-154e-cdcb-50cb6bd06dd7@linux.vnet.ibm.com \
--to=gpiccoli@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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).