DPDK patches and discussions
 help / color / mirror / Atom feed
From: Manish Chopra <manishc@marvell.com>
To: <jerinjacobk@gmail.com>, <jerinj@marvell.com>,
	<ferruh.yigit@intel.com>, <grive@u256.net>
Cc: <dev@dpdk.org>, <irusskikh@marvell.com>, <rmody@marvell.com>,
	<GR-Everest-DPDK-Dev@marvell.com>, <rosen.xu@intel.com>,
	<tianfei.zhang@intel.com>, <heinrich.kuhn@netronome.com>,
	<qiming.yang@intel.com>, <qi.z.zhang@intel.com>
Subject: [dpdk-dev] [PATCH v5 0/6] qede: SR-IOV PF driver support
Date: Thu, 30 Jul 2020 07:42:15 -0700	[thread overview]
Message-ID: <20200730144221.29051-1-manishc@marvell.com> (raw)

Hi,

This series adds SR-IOV PF pmd driver support to have VF pmd
driver work over PF pmd driver instances in order to run the
adapter completely under DPDK environment for one of the use
cases like ovs-dpdk.

This is very initial bring-up with following testing covered -

* Enable/Disable SR-IOV VFs through igb_uio sysfs hook.
* Load VFs, run fastpath, teardown VFs in hypervisor and guest VM.
* VF FLR flow (in case of VF PCI passthrough to the guest VM)
* Bulletin mechanism tested to communicate link changes to the VFs.

Note that this series is intended for upcoming DPDK release (20.08)
Please consider applying this series to dpdk-next-net-mrvl.git

V4->V5:
=======

* drivers/raw/ifpga was escaped to compile, test-robot reported
  below build failure which is fixed within patch #1 in this series.

'drivers/drivers@@tmp_rte_rawdev_ifpga@sta/raw_ifpga_ifpga_rawdev.c.o' -c ../drivers/raw/ifpga/ifpga_rawdev.c
../drivers/raw/ifpga/ifpga_rawdev.c: In function ‘ifpga_pci_find_next_ext_capability’:
../drivers/raw/ifpga/ifpga_rawdev.c:166:34: error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
   if (RTE_PCI_EXT_CAP_ID(header) == cap && pos != start)
                                  ^~
cc1: all warnings being treated as errors

V3->V4:
=======

* Fixed meson/ninja build failure for AMD arch.
* Incorporated cosmetic changes pointed by Gaetan.

V2->V3:
=======

* Instead of adding complete pci_regs.h file from linux, define handful
  PCI symbols (prefixed with RTE_) in dpdk which are required to implement
  generic rte_pci_find_next_ext_capability() API (patch #1) and to enable
  various other qede driver's OSAL_* defines (patch #2)
  (essentially, removed the patch #1 in v2)

* Fixed meson/ninja compilation issues reported

* Incorporated comments by Gaetan for rte_pci_find_next_ext_capability()

V1->V2: (Incorporated comments from Jerin Jacob)
================================================

* Added rte_pci_regs.h file (copy of linux/pci_regs.h) under
  lib/librte_pci to remove the dependency of dpdk on user headers

* Added generic API to find PCI extended capability and use
  that in the drivers, removed individual functions implemented
  by the drivers

Thanks,
Manish

Manish Chopra (6):
  drivers: add generic API to find PCI extended cap
  net/qede: define PCI config space specific osals
  net/qede: configure VFs on hardware
  net/qede: add infrastructure support for VF load
  net/qede: initialize VF MAC and link
  net/qede: add VF FLR support

 doc/guides/nics/features/qede.ini          |   1 +
 doc/guides/nics/qede.rst                   |   7 +-
 drivers/bus/pci/pci_common.c               |  43 ++++
 drivers/bus/pci/rte_bus_pci.h              |  20 ++
 drivers/bus/pci/rte_bus_pci_version.map    |   6 +
 drivers/net/ice/ice_ethdev.c               |  51 +----
 drivers/net/nfp/nfpcore/nfp_cpp_pcie_ops.c |  48 +----
 drivers/net/qede/Makefile                  |   1 +
 drivers/net/qede/base/bcm_osal.c           |  31 +++
 drivers/net/qede/base/bcm_osal.h           |  29 ++-
 drivers/net/qede/base/ecore.h              |   7 +
 drivers/net/qede/base/ecore_dev.c          |   6 +-
 drivers/net/qede/base/ecore_iov_api.h      |   3 +
 drivers/net/qede/base/ecore_sriov.c        |  28 +--
 drivers/net/qede/base/meson.build          |   2 +-
 drivers/net/qede/meson.build               |   1 +
 drivers/net/qede/qede_ethdev.c             |  37 +++-
 drivers/net/qede/qede_ethdev.h             |   1 +
 drivers/net/qede/qede_if.h                 |   1 +
 drivers/net/qede/qede_main.c               |  13 +-
 drivers/net/qede/qede_sriov.c              | 219 +++++++++++++++++++++
 drivers/net/qede/qede_sriov.h              |  22 +++
 drivers/raw/ifpga/ifpga_rawdev.c           |  17 +-
 lib/librte_pci/rte_pci.h                   |  35 ++++
 24 files changed, 488 insertions(+), 141 deletions(-)
 create mode 100644 drivers/net/qede/qede_sriov.c
 create mode 100644 drivers/net/qede/qede_sriov.h

-- 
2.17.1


             reply	other threads:[~2020-07-30 14:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-30 14:42 Manish Chopra [this message]
2020-07-30 14:42 ` [dpdk-dev] [PATCH v5 1/6] drivers: add generic API to find PCI extended cap Manish Chopra
2020-08-07 17:46   ` Nithin Dabilpuram
2020-07-30 14:42 ` [dpdk-dev] [PATCH v5 2/6] net/qede: define PCI config space specific osals Manish Chopra
2020-07-30 14:42 ` [dpdk-dev] [PATCH v5 3/6] net/qede: configure VFs on hardware Manish Chopra
2020-07-30 14:42 ` [dpdk-dev] [PATCH v5 4/6] net/qede: add infrastructure support for VF load Manish Chopra
2020-07-30 14:42 ` [dpdk-dev] [PATCH v5 5/6] net/qede: initialize VF MAC and link Manish Chopra
2020-07-30 14:42 ` [dpdk-dev] [PATCH v5 6/6] net/qede: add VF FLR support Manish Chopra

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=20200730144221.29051-1-manishc@marvell.com \
    --to=manishc@marvell.com \
    --cc=GR-Everest-DPDK-Dev@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=grive@u256.net \
    --cc=heinrich.kuhn@netronome.com \
    --cc=irusskikh@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=rmody@marvell.com \
    --cc=rosen.xu@intel.com \
    --cc=tianfei.zhang@intel.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).