From: Ding Tianhong <dingtianhong@huawei.com>
To: <leedom@chelsio.com>, <ashok.raj@intel.com>, <helgaas@kernel.org>,
<werner@chelsio.com>, <ganeshgr@chelsio.com>,
<asit.k.mallick@intel.com>, <patrick.j.cramer@intel.com>,
<Suravee.Suthikulpanit@amd.com>, <Bob.Shaw@amd.com>,
<l.stach@pengutronix.de>, <amira@mellanox.com>,
<gabriele.paoloni@huawei.com>, <David.Laight@aculab.com>,
<jeffrey.t.kirsher@intel.com>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <mark.rutland@arm.com>,
<robin.murphy@arm.com>, <davem@davemloft.net>,
<alexander.duyck@gmail.com>,
<linux-arm-kernel@lists.infradead.org>, <netdev@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 0/3] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag
Date: Thu, 29 Jun 2017 13:47:23 +0800 [thread overview]
Message-ID: <43e01fca-a746-90d2-fdfa-c63f1d56ef5f@huawei.com> (raw)
In-Reply-To: <1498133721-21152-1-git-send-email-dingtianhong@huawei.com>
ping
On 2017/6/22 20:15, Ding Tianhong wrote:
> Some devices have problems with Transaction Layer Packets with the Relaxed
> Ordering Attribute set. This patch set adds a new PCIe Device Flag,
> PCI_DEV_FLAGS_NO_RELAXED_ORDERING, a set of PCI Quirks to catch some known
> devices with Relaxed Ordering issues, and a use of this new flag by the
> cxgb4 driver to avoid using Relaxed Ordering with problematic Root Complex
> Ports.
>
> It's been years since I've submitted kernel.org patches, I appolgise for the
> almost certain submission errors.
>
> v2: Alexander point out that the v1 was only a part of the whole solution,
> some platform which has some issues could use the new flag to indicate
> that it is not safe to enable relaxed ordering attribute, then we need
> to clear the relaxed ordering enable bits in the PCI configuration when
> initializing the device. So add a new second patch to modify the PCI
> initialization code to clear the relaxed ordering enable bit in the
> event that the root complex doesn't want relaxed ordering enabled.
>
> The third patch was base on the v1's second patch and only be changed
> to query the relaxed ordering enable bit in the PCI configuration space
> to allow the Chelsio NIC to send TLPs with the relaxed ordering attributes
> set.
>
> This version didn't plan to drop the defines for Intel Drivers to use the
> new checking way to enable relaxed ordering because it is not the hardest
> part of the moment, we could fix it in next patchset when this patches
> reach the goal.
>
> v3: Redesigned the logic for pci_configure_relaxed_ordering when configuration,
> If a PCIe device didn't enable the relaxed ordering attribute default,
> we should not do anything in the PCIe configuration, otherwise we
> should check if any of the devices above us do not support relaxed
> ordering by the PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag, then base on
> the result if we get a return that indicate that the relaxed ordering
> is not supported we should update our device to disable relaxed ordering
> in configuration space. If the device above us doesn't exist or isn't
> the PCIe device, we shouldn't do anything and skip updating relaxed ordering
> because we are probably running in a guest.
>
> v4: Rename the functions pcie_get_relaxed_ordering and pcie_disable_relaxed_ordering
> according John's suggestion, and modify the description, use the true/false
> as the return value.
>
> We shouldn't enable relaxed ordering attribute by the setting in the root
> complex configuration space for PCIe device, so fix it for cxgb4.
>
> Fix some format issues.
>
> v5: Removed the unnecessary code for some function which only return the bool
> value, and add the check for VF device.
>
> Make this patch set base on 4.12-rc5.
>
> v6: Fix the logic error in the need to enable the relaxed ordering attribute for cxgb4.
>
> Casey Leedom (2):
> PCI: Add new PCIe Fabric End Node flag,
> PCI_DEV_FLAGS_NO_RELAXED_ORDERING
> net/cxgb4: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag
>
> Ding Tianhong (1):
> PCI: Enable PCIe Relaxed Ordering if supported
>
> drivers/net/ethernet/chelsio/cxgb4/cxgb4.h | 1 +
> drivers/net/ethernet/chelsio/cxgb4/cxgb4_main.c | 17 ++++++++++
> drivers/net/ethernet/chelsio/cxgb4/sge.c | 5 +--
> drivers/pci/pci.c | 32 +++++++++++++++++++
> drivers/pci/probe.c | 41 +++++++++++++++++++++++++
> drivers/pci/quirks.c | 38 +++++++++++++++++++++++
> include/linux/pci.h | 4 +++
> 7 files changed, 136 insertions(+), 2 deletions(-)
>
next prev parent reply other threads:[~2017-06-29 5:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 12:15 [PATCH v6 0/3] Add new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag Ding Tianhong
2017-06-22 12:15 ` [PATCH v6 1/3] PCI: Add new PCIe Fabric End Node flag, PCI_DEV_FLAGS_NO_RELAXED_ORDERING Ding Tianhong
2017-06-22 12:15 ` [PATCH v6 2/3] PCI: Enable PCIe Relaxed Ordering if supported Ding Tianhong
2017-06-22 12:15 ` [PATCH v6 3/3] net/cxgb4: Use new PCI_DEV_FLAGS_NO_RELAXED_ORDERING flag Ding Tianhong
2017-06-29 5:47 ` Ding Tianhong [this message]
2017-07-06 12:58 ` [PATCH v6 0/3] Add " Ding Tianhong
2017-07-06 17:17 ` Bjorn Helgaas
2017-07-07 1:03 ` Ding Tianhong
2017-07-07 21:48 ` Casey Leedom
2017-07-08 0:30 ` Casey Leedom
2017-07-08 0:47 ` Alexander Duyck
2017-07-08 2:04 ` Casey Leedom
2017-07-08 3:37 ` Alexander Duyck
2017-07-11 0:01 ` Casey Leedom
2017-07-11 20:33 ` Alexander Duyck
2017-07-12 9:46 ` Ding Tianhong
2017-07-13 0:52 ` Casey Leedom
2017-07-13 1:18 ` Ding Tianhong
2017-07-13 2:28 ` Casey Leedom
2017-07-10 10:49 ` 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=43e01fca-a746-90d2-fdfa-c63f1d56ef5f@huawei.com \
--to=dingtianhong@huawei.com \
--cc=Bob.Shaw@amd.com \
--cc=David.Laight@aculab.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=alexander.duyck@gmail.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=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.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--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).