From: Gavin Shan <gwshan@linux.vnet.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Gavin Shan <gwshan@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, stable@vger.kernel.org,
#v4.9+@gwshan.ozlabs.ibm.com
Subject: Re: [PATCH] drivers/pci/hotplug: Handle presence detection change properly
Date: Wed, 21 Dec 2016 10:06:57 +1100 [thread overview]
Message-ID: <20161220230657.GA7066@gwshan> (raw)
In-Reply-To: <20161220093709.GA12938@kroah.com>
On Tue, Dec 20, 2016 at 10:37:09AM +0100, Greg KH wrote:
>On Tue, Dec 20, 2016 at 05:49:33PM +1100, Gavin Shan wrote:
>> The surprise hotplug is driven by interrupt in PowerNV PCI hotplug
>> driver. In the interrupt handler, pnv_php_interrupt(), we bail when
>> pnv_pci_get_presence_state() returns zero wrongly. It causes the
>> presence change event is always ignored incorrectly.
>>
>> This fixes the issue by bailing on error (non-zero value) returned
>> from pnv_pci_get_presence_state().
>>
>> Fixes: 360aebd85a4 ("drivers/pci/hotplug: Support surprise hotplug in powernv driver")
>> Cc: stable@vger.kernel.org #v4.9+
>> Reported-by: Hank Chang <hankmax0000@gmail.com>
>> Signed-off-by: Gavin Shan <gwshan@linux.vnet.ibm.com>
>> Tested-by: Willie Liauw <williel@supermicro.com.tw>
>> ---
>> drivers/pci/hotplug/pnv_php.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/pci/hotplug/pnv_php.c b/drivers/pci/hotplug/pnv_php.c
>> index 56efaf7..38a2309 100644
>> --- a/drivers/pci/hotplug/pnv_php.c
>> +++ b/drivers/pci/hotplug/pnv_php.c
>> @@ -707,8 +707,12 @@ static irqreturn_t pnv_php_interrupt(int irq, void *data)
>> added = !!(lsts & PCI_EXP_LNKSTA_DLLLA);
>> } else if (sts & PCI_EXP_SLTSTA_PDC) {
>> ret = pnv_pci_get_presence_state(php_slot->id, &presence);
>> - if (!ret)
>> + if (ret) {
>> + dev_warn(&pdev->dev, "PCI slot [%s] error %d handling PDC event (0x%04x)\n",
>> + php_slot->name, ret, sts);
>
>What can a user do with this warning?
>
This warning is to catch developer's attention only. It's very
rare for pnv_pci_get_presence_state() to fail as it simply checks
hardware regiter bit (from Slot Status regsiter in PCIe capability
or PHB's Hotplug Override register) in the skiboot firmware.
User needs to retry the operation (hot-add or hot-remove) when
seeing this warning. Greg, please let me know if below message
is better?
dev_warn(&pdev->dev, "PCI slot [%s] error %d getting presence status on event 0x%04x, to retry the operation.\n",
php_slot->name, ret, sts);
Thanks,
Gavin
next prev parent reply other threads:[~2016-12-20 23:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-20 6:49 [PATCH] drivers/pci/hotplug: Handle presence detection change properly Gavin Shan
2016-12-20 9:37 ` Greg KH
2016-12-20 23:06 ` Gavin Shan [this message]
2016-12-22 4:26 ` 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=20161220230657.GA7066@gwshan \
--to=gwshan@linux.vnet.ibm.com \
--cc=#v4.9+@gwshan.ozlabs.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stable@vger.kernel.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).