From: Alexander Duyck <alexander.duyck@gmail.com>
To: Ding Tianhong <dingtianhong@huawei.com>
Cc: Casey Leedom <leedom@chelsio.com>,
Ashok Raj <ashok.raj@intel.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Michael Werner <werner@chelsio.com>,
Ganesh Goudar <ganeshgr@chelsio.com>,
Asit K Mallick <asit.k.mallick@intel.com>,
Patrick J Cramer <patrick.j.cramer@intel.com>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>,
Bob Shaw <Bob.Shaw@amd.com>, h <l.stach@pengutronix.de>,
Amir Ancel <amira@mellanox.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
David Laight <David.Laight@aculab.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
David Miller <davem@davemloft.net>,
linux-arm-kernel@lists.inf
Subject: Re: [PATCH v4 2/3] PCI: Enable PCIe Relaxed Ordering if supported
Date: Fri, 16 Jun 2017 07:39:30 -0700 [thread overview]
Message-ID: <CAKgT0UfefJ8E6m215Caxekd-OugOuZxyS5N3t_q07OTEHHd0xw@mail.gmail.com> (raw)
In-Reply-To: <5854930e-af6a-4274-2822-cf38e5967da3@huawei.com>
On Thu, Jun 15, 2017 at 6:10 PM, Ding Tianhong <dingtianhong@huawei.com> wrote:
>
>
> On 2017/6/13 5:28, Alexander Duyck wrote:
>> On Mon, Jun 12, 2017 at 4:05 AM, Ding Tianhong <dingtianhong@huawei.com> wrote:
> ...
>>> /**
>>> + * pcie_clear_relaxed_ordering - clear PCI Express relaxed ordering bit
>>> + * @dev: PCI device to query
>>> + *
>>> + * If possible clear relaxed ordering
>>> + */
>>> +int pcie_clear_relaxed_ordering(struct pci_dev *dev)
>>> +{
>>> + return pcie_capability_clear_word(dev, PCI_EXP_DEVCTL,
>>> + PCI_EXP_DEVCTL_RELAX_EN);
>>> +}
>>> +EXPORT_SYMBOL(pcie_clear_relaxed_ordering);
>>> +
>>> +/**
>>> + * pcie_relaxed_ordering_supported - Probe for PCIe relexed ordering support
>>> + * @dev: PCI device to query
>>> + *
>>> + * Returns true if the device support relaxed ordering attribute.
>>> + */
>>> +bool pcie_relaxed_ordering_supported(struct pci_dev *dev)
>>> +{
>>> + bool ro_supported = false;
>>> + u16 v;
>>> +
>>> + pcie_capability_read_word(dev, PCI_EXP_DEVCTL, &v);
>>> + if ((v & PCI_EXP_DEVCTL_RELAX_EN) >> 4)
>>> + ro_supported = true;
>>
>> Instead of "return ro_supported" why not just "return !!(v &
>> PCIE_EXP_DEVCTL_RELAX_EN)"? You can cut out the extra steps and save
>> yourself some extra steps this way since the shift by 4 shouldn't even
>> really be needed since you are just testing for a bit anyway.
>>
>
> OK.
>
>>> +
>>> + return ro_supported;
>>> +}
>>> +EXPORT_SYMBOL(pcie_relaxed_ordering_supported);
>>> +
>>> +/**
>>> * pcie_get_minimum_link - determine minimum link settings of a PCI device
>>> * @dev: PCI device to query
>>> * @speed: storage for minimum speed
>>> diff --git a/drivers/pci/probe.c b/drivers/pci/probe.c
>>> index 19c8950..ed1f717 100644
>>> --- a/drivers/pci/probe.c
>>> +++ b/drivers/pci/probe.c
>>> @@ -1701,6 +1701,46 @@ static void pci_configure_extended_tags(struct pci_dev *dev)
>>> PCI_EXP_DEVCTL_EXT_TAG);
>>> }
>>>
>>> +/**
>>> + * pci_dev_should_disable_relaxed_ordering - check if the PCI device
>>> + * should disable the relaxed ordering attribute.
>>> + * @dev: PCI device
>>> + *
>>> + * Return true if any of the PCI devices above us do not support
>>> + * relaxed ordering.
>>> + */
>>> +static bool pci_dev_should_disable_relaxed_ordering(struct pci_dev *dev)
>>> +{
>>> + bool ro_disabled = false;
>>> +
>>> + while (dev) {
>>> + if (dev->dev_flags & PCI_DEV_FLAGS_NO_RELAXED_ORDERING) {
>>> + ro_disabled = true;
>>> + break;
>>> + }
>>> + dev = dev->bus->self;
>>> + }
>>> +
>>> + return ro_disabled;
>>
>> Same thing here. I would suggest just returning either true or false,
>> and drop the ro_disabled value. It will return the lines of code and
>> make things a bit bit more direct.
>>
>
> OK.
>
>>> +}
>>> +
>>> +static void pci_configure_relaxed_ordering(struct pci_dev *dev)
>>> +{
>>> + struct pci_dev *bridge = pci_upstream_bridge(dev);
>>> +
>>> + if (!pci_is_pcie(dev) || !bridge || !pci_is_pcie(bridge))
>>> + return;
>>
>> The pci_is_pcie check is actually redundant based on the
>> pcie_relaxed_ordering_supported check using pcie_capability_read_word.
>>
>
> Yes, pcie_capability_read_word already check it, thanks.
>
>
>> Also I am not sure what the point is of the pci_upstream_bridge()
>> check is, it seems like you should be able to catch all the same stuff
>> in your pci_dev_should_disable_relaxed_ordering() call. Though it did
>> give me a thought. I don't think we can alter this for a VF, so you
>> might want to add a check for dev->is_virtfn to the list of checks and
>> if it is a virtual function just return since I don't think there are
>> any VFs that would let you alter this bit anyway.
>>
> If the upstream device is null, does it mean that it is in a guest OS device? maybe I miss something.
> also I will check the dev->is_virtfn to avoid trying to change the configuration space for VF.
Yes, usually the upstream device is NULL in guest setups where all the
devices are hung off of a single PCI bus.
> Another question: Because it looks like that maybe the Casey is too busy these days, should we
> delay the modification of the cxgb4 and instead to update the ixgbe? what do you think about it. :)
I would still submit the cxgb4 changes with the one change we have
made. It should work as is. We can just leave any follow-up work to
Casey in terms of enabling the peer-to-peer mode if the bits related
to relaxed ordering are cleared.
> Thanks.
> Ding
>
>>> + /* If the releaxed ordering enable bit is not set, do nothing. */
>>> + if (!pcie_relaxed_ordering_supported(dev))
>>> + return;
>>> +
>>> + if (pci_dev_should_disable_relaxed_ordering(dev)) {
>>> + pcie_clear_relaxed_ordering(dev);
>>> + dev_info(&dev->dev, "Disable Relaxed Ordering\n");
>>> + }
>>> +}
>>> +
>>> static void pci_configure_device(struct pci_dev *dev)
>>> {
>>> struct hotplug_params hpp;
>>> @@ -1708,6 +1748,7 @@ static void pci_configure_device(struct pci_dev *dev)
>>>
>>> pci_configure_mps(dev);
>>> pci_configure_extended_tags(dev);
>>> + pci_configure_relaxed_ordering(dev);
>>>
>>> memset(&hpp, 0, sizeof(hpp));
>>> ret = pci_get_hp_params(dev, &hpp);
>>> diff --git a/include/linux/pci.h b/include/linux/pci.h
>>> index e1e8428..9870781 100644
>>> --- a/include/linux/pci.h
>>> +++ b/include/linux/pci.h
>>> @@ -1105,6 +1105,8 @@ int __pci_enable_wake(struct pci_dev *dev, pci_power_t state,
>>> void pci_pme_wakeup_bus(struct pci_bus *bus);
>>> void pci_d3cold_enable(struct pci_dev *dev);
>>> void pci_d3cold_disable(struct pci_dev *dev);
>>> +int pcie_clear_relaxed_ordering(struct pci_dev *dev);
>>> +bool pcie_relaxed_ordering_supported(struct pci_dev *dev);
>>>
>>> static inline int pci_enable_wake(struct pci_dev *dev, pci_power_t state,
>>> bool enable)
>>> --
>>> 1.9.0
>>>
>>>
>>
>> .
>>
>
next prev parent reply other threads:[~2017-06-16 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 11:05 [PATCH v4 0/3] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag Ding Tianhong
2017-06-12 11:05 ` [PATCH v4 1/3] PCI: Add new PCIe Fabric End Node flag, PCI_DEV_FLAGS_NO_RELAXED_ORDERING Ding Tianhong
2017-06-12 11:05 ` [PATCH v4 2/3] PCI: Enable PCIe Relaxed Ordering if supported Ding Tianhong
2017-06-12 21:28 ` Alexander Duyck
2017-06-16 1:10 ` Ding Tianhong
2017-06-16 14:39 ` Alexander Duyck [this message]
2017-06-19 6:12 ` Ding Tianhong
2017-06-12 11:05 ` [PATCH v4 3/3] net/cxgb4: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag Ding Tianhong
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=CAKgT0UfefJ8E6m215Caxekd-OugOuZxyS5N3t_q07OTEHHd0xw@mail.gmail.com \
--to=alexander.duyck@gmail.com \
--cc=Bob.Shaw@amd.com \
--cc=David.Laight@aculab.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=amira@mellanox.com \
--cc=ashok.raj@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=dingtianhong@huawei.com \
--cc=gabriele.paoloni@huawei.com \
--cc=ganeshgr@chelsio.com \
--cc=helgaas@kernel.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=l.stach@pengutronix.de \
--cc=leedom@chelsio.com \
--cc=linux-arm-kernel@lists.inf \
--cc=mark.rutland@arm.com \
--cc=patrick.j.cramer@intel.com \
--cc=robin.murphy@arm.com \
--cc=werner@chelsio.com \
--cc=will.deacon@arm.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).