From: Bjorn Helgaas <bhelgaas@google.com>
To: Gavin Shan <gwshan@linux.vnet.ibm.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Richard Yang <weiyang@linux.vnet.ibm.com>
Subject: Re: [PATCH] PCI: Make reset warning messages different
Date: Wed, 15 Oct 2014 21:43:32 -0600 [thread overview]
Message-ID: <CAErSpo44eZJitWqLnY2wopLPT7BiDFcFAKuh8K-m8X30-VMNdQ@mail.gmail.com> (raw)
In-Reply-To: <20141016001920.GA18777@shangw>
On Wed, Oct 15, 2014 at 6:19 PM, Gavin Shan <gwshan@linux.vnet.ibm.com> wrote:
> On Wed, Oct 15, 2014 at 05:48:35PM -0600, Bjorn Helgaas wrote:
>>On Wed, Oct 15, 2014 at 5:41 PM, Gavin Shan <gwshan@linux.vnet.ibm.com> wrote:
>>> We have same warning message for FLR and AF FLR and users can't
>>> know which type of resets the PCI device is taking when there are
>>> pending transactions. The patch makes them different for FLR and
>>> AF FLR cases.
>>>
>>> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>>> ---
>>> drivers/pci/pci.c | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c
>>> index 625a4ac..2d708cd 100644
>>> --- a/drivers/pci/pci.c
>>> +++ b/drivers/pci/pci.c
>>> @@ -3144,7 +3144,7 @@ static int pcie_flr(struct pci_dev *dev, int probe)
>>> return 0;
>>>
>>> if (!pci_wait_for_pending_transaction(dev))
>>> - dev_err(&dev->dev, "transaction is not cleared; proceeding with reset anyway\n");
>>> + dev_err(&dev->dev, "Force FLR with pending transaction\n");
>>>
>>> pcie_capability_set_word(dev, PCI_EXP_DEVCTL, PCI_EXP_DEVCTL_BCR_FLR);
>>>
>>> @@ -3178,7 +3178,7 @@ static int pci_af_flr(struct pci_dev *dev, int probe)
>>> PCI_AF_STATUS_TP << 8))
>>> goto clear;
>>>
>>> - dev_err(&dev->dev, "transaction is not cleared; proceeding with reset anyway\n");
>>> + dev_err(&dev->dev, "Force AF FLR with pending transaction\n");
>>
>>Making the text different is fine, but I don't think "FLR" and "AF
>>FLR" are meaningful except to extremely technical people. So I think
>>"reset" needs to stay spelled out in the message.
>>
>
> Agree, it's worthy to keep "reset". How about something like this:
>
> "Force function level reset with pending transaction" - FLR
> "Force AF function level reset with pending transaction" - AF FLR
>
> If above messages look good to you, I'll send out another revision.
How about something like "timed out waiting for pending transaction;
performing function level reset"?
"Force reset with pending transaction" sounds like a pending
transaction might be the mechanism we're using to perform the reset.
Out of curiosity, is there some issue you tripped over where it's
important for users to know this difference?
Just FYI, I'll be on vacation the rest of this week.
Bjorn
next prev parent reply other threads:[~2014-10-16 3:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 23:41 [PATCH] PCI: Make reset warning messages different Gavin Shan
2014-10-15 23:48 ` Bjorn Helgaas
2014-10-16 0:19 ` Gavin Shan
2014-10-16 3:43 ` Bjorn Helgaas [this message]
2014-10-16 4:59 ` Gavin Shan
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=CAErSpo44eZJitWqLnY2wopLPT7BiDFcFAKuh8K-m8X30-VMNdQ@mail.gmail.com \
--to=bhelgaas@google.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux-pci@vger.kernel.org \
--cc=weiyang@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).