linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dongdong Liu <liudongdong3@huawei.com>
To: <helgaas@kernel.org>, <linux-pci@vger.kernel.org>
Subject: [PATCH 0/4] PCI: Enable 10-Bit tag support for PCIe devices
Date: Sat, 3 Apr 2021 16:54:15 +0800	[thread overview]
Message-ID: <1617440059-2478-1-git-send-email-liudongdong3@huawei.com> (raw)

10-Bit Tag capability, introduced in PCIe-4.0 increases the total Tag
field size from 8 bits to 10 bits.

This patchset is to enable 10-Bit tag for PCIe EP devices (include VF) and
RP devices.

Dongdong Liu (4):
  PCI: Add 10-Bit Tag register definitions
  PCI: Enable 10-Bit tag support for PCIe Endpoint devices
  PCI/IOV: Enable 10-Bit tag support for PCIe VF devices
  PCI: Enable 10-Bit tag support for PCIe RP devices

 drivers/pci/iov.c              |   8 +++
 drivers/pci/pci.h              |   2 +
 drivers/pci/pcie/portdrv_pci.c |   3 +
 drivers/pci/probe.c            | 125 +++++++++++++++++++++++++++++++++++++++++
 include/linux/pci.h            |   1 +
 include/uapi/linux/pci_regs.h  |   5 ++
 6 files changed, 144 insertions(+)

--
1.9.1


             reply	other threads:[~2021-04-03  9:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-03  8:54 Dongdong Liu [this message]
2021-04-03  8:54 ` [PATCH 1/4] PCI: Add 10-Bit Tag register definitions Dongdong Liu
2021-04-03  8:54 ` [PATCH 2/4] PCI: Enable 10-Bit tag support for PCIe Endpoint devices Dongdong Liu
2021-04-03  9:50   ` Christoph Hellwig
2021-04-06  2:33     ` Dongdong Liu
2021-04-03  8:54 ` [PATCH 3/4] PCI/IOV: Enable 10-Bit tag support for PCIe VF devices Dongdong Liu
2021-04-03  8:54 ` [PATCH 4/4] PCI: Enable 10-Bit tag support for PCIe RP devices Dongdong Liu
2021-04-03 10:32   ` kernel test robot
2021-04-03 12:33   ` kernel test robot
2021-04-06  2:41     ` Dongdong Liu

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=1617440059-2478-1-git-send-email-liudongdong3@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 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).