DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Jan Viktorin <viktorin@rehivetech.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: David Marchand <david.marchand@6wind.com>,
	"Wiles, Keith" <keith.wiles@intel.com>,
	Santosh Shukla <sshukla@mvista.com>,
	"Stephen Hemminger" <stephen@networkplumber.org>,
	Shreyansh Jain <shreyansh.jain@nxp.com>
Subject: Re: [dpdk-dev] [PATCH v3 00/16] Make VFIO support less dependent on PCI
Date: Mon, 4 Jul 2016 15:26:27 +0000	[thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E4512369782130862@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1467645411-15494-1-git-send-email-viktorin@rehivetech.com>

> From: Jan Viktorin [mailto:viktorin@rehivetech.com]
> Sent: Monday, July 4, 2016 4:17 PM
> To: dev@dpdk.org
> Cc: Jan Viktorin <viktorin@rehivetech.com>; Burakov, Anatoly
> <anatoly.burakov@intel.com>; David Marchand
> <david.marchand@6wind.com>; Wiles, Keith <keith.wiles@intel.com>;
> Santosh Shukla <sshukla@mvista.com>; Stephen Hemminger
> <stephen@networkplumber.org>; Shreyansh Jain
> <shreyansh.jain@nxp.com>
> Subject: [PATCH v3 00/16] Make VFIO support less dependent on PCI
> 
> Hello,
> 
> I've rebased the v2 of this patch set on top of the current master.
> It builds well for my setup (both VFIO enabled and disabled).
> 
> Regards
> Jan
> 
> 
> v3:
> * 0012: Acked-by: John McNamara <john.mcnamara@intel.com>
> 
> Jan Viktorin (16):
>   vfio: fix include of eal_private.h to be local
>   vfio: move VFIO-specific stuff to eal_vfio.h
>   vfio: move common vfio constants to eal_vfio.h
>   vfio: move vfio_iommu_type and dma_map functions to eal_vfio
>   vfio: generalize pci_vfio_set_iommu_type
>   vfio: generalize pci_vfio_has_supported_extensions
>   vfio: move vfio-specific SOCKET_* constants
>   vfio: generalize pci_vfio_get_container_fd
>   vfio: generalize pci_vfio_get_group_no
>   vfio: extract setup logic out of pci_vfio_map_resource
>   vfio: move global vfio_cfg to eal_vfio.c
>   vfio: fix typo in doc for vfio_setup_device
>   vfio: make vfio_*_dma_map and iommu_types private
>   vfio: rename and generalize eal_pci_vfio_mp_sync
>   vfio: initialize vfio out of the PCI subsystem
>   vfio: change VFIO init to be extendable
> 
>  lib/librte_eal/linuxapp/eal/Makefile               |   5 +-
>  lib/librte_eal/linuxapp/eal/eal.c                  |  33 ++
>  lib/librte_eal/linuxapp/eal/eal_pci.c              |  17 +-
>  lib/librte_eal/linuxapp/eal/eal_pci_init.h         |  41 --
>  lib/librte_eal/linuxapp/eal/eal_pci_vfio.c         | 517 +------------------
>  lib/librte_eal/linuxapp/eal/eal_vfio.c             | 547 +++++++++++++++++++++
>  lib/librte_eal/linuxapp/eal/eal_vfio.h             |  94 ++++
>  .../{eal_pci_vfio_mp_sync.c => eal_vfio_mp_sync.c} |  12 +-
>  8 files changed, 691 insertions(+), 575 deletions(-)  create mode 100644
> lib/librte_eal/linuxapp/eal/eal_vfio.c
>  rename lib/librte_eal/linuxapp/eal/{eal_pci_vfio_mp_sync.c =>
> eal_vfio_mp_sync.c} (97%)
> 
> --
> 2.8.0

For the whole patchset:

Acked-by: Anatoly  Burakov <anatoly.burakov@intel.com>

  parent reply	other threads:[~2016-07-04 15:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 15:16 Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 01/16] vfio: fix include of eal_private.h to be local Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 02/16] vfio: move VFIO-specific stuff to eal_vfio.h Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 03/16] vfio: move common vfio constants " Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 04/16] vfio: move vfio_iommu_type and dma_map functions to eal_vfio Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 05/16] vfio: generalize pci_vfio_set_iommu_type Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 06/16] vfio: generalize pci_vfio_has_supported_extensions Jan Viktorin
2016-07-10 17:36   ` Thomas Monjalon
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 07/16] vfio: move vfio-specific SOCKET_* constants Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 08/16] vfio: generalize pci_vfio_get_container_fd Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 09/16] vfio: generalize pci_vfio_get_group_no Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 10/16] vfio: extract setup logic out of pci_vfio_map_resource Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 11/16] vfio: move global vfio_cfg to eal_vfio.c Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 12/16] vfio: fix typo in doc for vfio_setup_device Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 13/16] vfio: make vfio_*_dma_map and iommu_types private Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 14/16] vfio: rename and generalize eal_pci_vfio_mp_sync Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 15/16] vfio: initialize vfio out of the PCI subsystem Jan Viktorin
2016-07-04 15:16 ` [dpdk-dev] [PATCH v3 16/16] vfio: change VFIO init to be extendable Jan Viktorin
2016-07-04 15:26 ` Burakov, Anatoly [this message]
2016-07-10 18:17 ` [dpdk-dev] [PATCH v3 00/16] Make VFIO support less dependent on PCI Thomas Monjalon

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=C6ECDF3AB251BE4894318F4E4512369782130862@IRSMSX109.ger.corp.intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=david.marchand@6wind.com \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=shreyansh.jain@nxp.com \
    --cc=sshukla@mvista.com \
    --cc=stephen@networkplumber.org \
    --cc=viktorin@rehivetech.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).