From: Dongdong Liu <liudongdong3@huawei.com>
To: <helgaas@kernel.org>, <linux-pci@vger.kernel.org>
Subject: Re: [RFC PATCH 0/3] PCI: Enable 10-bit tags support for PCIe devices
Date: Tue, 9 Feb 2021 21:18:35 +0800 [thread overview]
Message-ID: <f8f98eb8-d2d4-94d7-75c9-6e0520e60c2a@huawei.com> (raw)
In-Reply-To: <1610183483-2061-1-git-send-email-liudongdong3@huawei.com>
kindly ping :)
On 2021/1/9 17:11, Dongdong Liu wrote:
> 10-Bit Tag capability, introduced in PCIe-4.0 increases the total Tag
> field size from 8 bits to 10 bits.
>
> For platforms where the RC supports 10-Bit Tag Completer capability,
> it is highly recommended for platform firmware or operating software
> that configures PCIe hierarchies to Set the 10-Bit Tag Requester Enable
> bit automatically in Endpoints with 10-Bit Tag Requester capability. This
> enables the important class of 10-Bit Tag capable adapters that send
> Memory Read Requests only to host memory.
>
> This patchset is to enable 10-bits for PCIe EP devices.
>
> Dongdong Liu (3):
> PCI: Add 10-Bit Tag register definitions
> PCI: Enable 10-bit tags support for PCIe devices
> PCI/IOV: Enable 10-bit tags support for PCIe VF devices
>
> drivers/pci/iov.c | 8 ++++++++
> drivers/pci/probe.c | 39 +++++++++++++++++++++++++++++++++++++++
> include/linux/pci.h | 1 +
> include/uapi/linux/pci_regs.h | 5 +++++
> 4 files changed, 53 insertions(+)
>
> --
> 1.9.1
>
> .
>
prev parent reply other threads:[~2021-02-09 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-09 9:11 [RFC PATCH 0/3] PCI: Enable 10-bit tags support for PCIe devices Dongdong Liu
2021-01-09 9:11 ` [RFC PATCH 1/3] PCI: Add 10-Bit Tag register definitions Dongdong Liu
2021-01-09 9:11 ` [RFC PATCH 2/3] PCI: Enable 10-bit tags support for PCIe devices Dongdong Liu
2021-01-09 9:11 ` [RFC PATCH 3/3] PCI/IOV: Enable 10-bit tags support for PCIe VF devices Dongdong Liu
2021-02-09 13:18 ` Dongdong Liu [this message]
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=f8f98eb8-d2d4-94d7-75c9-6e0520e60c2a@huawei.com \
--to=liudongdong3@huawei.com \
--cc=helgaas@kernel.org \
--cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.