From: Gavin Shan <shangw@linux.vnet.ibm.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: Gavin Shan <shangw@linux.vnet.ibm.com>,
Hanjun Guo <guohanjun@huawei.com>,
linux-kernel@vger.kernel.org,
"James E.J. Bottomley" <JBottomley@parallels.com>,
Paul Mackerras <paulus@samba.org>,
linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 3/6] powerpc/pci: use pci_is_pcie() to simplify code
Date: Fri, 11 Oct 2013 14:53:29 +0800 [thread overview]
Message-ID: <20131011065329.GA5013@shangw.(null)> (raw)
In-Reply-To: <52579BD6.40802@huawei.com>
On Fri, Oct 11, 2013 at 02:33:58PM +0800, Yijing Wang wrote:
>On 2013/10/11 14:16, Gavin Shan wrote:
>> On Fri, Oct 11, 2013 at 04:49:56PM +1100, Benjamin Herrenschmidt wrote:
>>> On Fri, 2013-09-06 at 14:30 -0600, Bjorn Helgaas wrote:
>>>> On Thu, Sep 05, 2013 at 03:55:27PM +0800, Yijing Wang wrote:
.../...
>>>>> Use pci_is_pcie() to simplify code.
>>>>> diff --git a/arch/powerpc/kernel/eeh.c b/arch/powerpc/kernel/eeh.c
>>>>> index 55593ee..6ebbe54 100644
>>>>> --- a/arch/powerpc/kernel/eeh.c
>>>>> +++ b/arch/powerpc/kernel/eeh.c
>>>>> @@ -189,8 +189,7 @@ static size_t eeh_gather_pci_data(struct eeh_dev *edev, char * buf, size_t len)
>>>>> }
>>>>>
>>>>> /* If PCI-E capable, dump PCI-E cap 10, and the AER */
>>>>> - cap = pci_find_capability(dev, PCI_CAP_ID_EXP);
>>>>> - if (cap) {
>>>>> + if (pci_is_pcie(dev)) {
>>>>> n += scnprintf(buf+n, len-n, "pci-e cap10:\n");
>>>>> printk(KERN_WARNING
>>>>> "EEH: PCI-E capabilities and status follow:\n");
>>>
>>> So we remove reading of "cap", but slightly further down the code does:
>>>
>>> for (i=0; i<=8; i++) {
>>> eeh_ops->read_config(dn, cap+4*i, 4, &cfg);
>>> n += scnprintf(buf+n, len-n, "%02x:%x\n", 4*i, cfg);
>>> printk(KERN_WARNING "EEH: PCI-E %02x: %08x\n", i, cfg);
>>> }
>>>
>>> Which actually *uses* the value of "cap" ... oops :-)
>>>
>>
>> It's my fault and I should have looked into the changes more closely.
>> How about changing it like this:
>>
>> cap = pci_is_pcie(dev) ? pci_pcie_cap(dev) :
>> pci_find_capability(dev, PCI_CAP_ID_EXP);
>> if (cap) {
>> ...
>> }
>>
>> It would save some PCI-CFG access cycles for most cases :-)
>
>Hi Gavin, it's not your fault, it's my fault. :)
>
>Because pci_pcie_cap(dev) == dev->pcie_cap == pci_find_capability(dev, PCI_CAP_ID_EXP);
>
>so I think it's ok to use dev->pcie_cap instead of stale "cap".
>
Yijing, There has one exception: dev->pcie_cap isn't updated yet.
This function has possibility to be invoked before that. However,
we don't have the binding (eeh device <-> PCI device) for the case.
So the piece of code shouldn't be running
However, it's a bit safer to have pci_find_capability(dev, PCI_CAP_ID_EXP)
as well even though we needn't it for 99.9% cases if you agree :-)
Thanks,
Gavin
next prev parent reply other threads:[~2013-10-11 6:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1378367730-25996-1-git-send-email-wangyijing@huawei.com>
2013-09-05 7:55 ` [PATCH v2 3/6] powerpc/pci: use pci_is_pcie() to simplify code Yijing Wang
2013-09-06 20:30 ` Bjorn Helgaas
2013-10-11 5:49 ` Benjamin Herrenschmidt
2013-10-11 6:16 ` Gavin Shan
2013-10-11 6:33 ` Yijing Wang
2013-10-11 6:53 ` Gavin Shan [this message]
2013-10-11 7:28 ` Yijing Wang
2013-10-11 7:56 ` Gavin Shan
2013-10-11 8:22 ` Yijing Wang
2013-10-11 6:28 ` Yijing Wang
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='20131011065329.GA5013@shangw.(null)' \
--to=shangw@linux.vnet.ibm.com \
--cc=JBottomley@parallels.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=wangyijing@huawei.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).