DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jan Viktorin <viktorin@rehivetech.com>
Cc: dev@dpdk.org, Anatoly Burakov <anatoly.burakov@intel.com>,
	David Marchand <david.marchand@6wind.com>,
	Keith Wiles <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 06/16] vfio: generalize pci_vfio_has_supported_extensions
Date: Sun, 10 Jul 2016 19:36:57 +0200	[thread overview]
Message-ID: <2658506.JKWTbPl3g7@xps13> (raw)
In-Reply-To: <1467645411-15494-7-git-send-email-viktorin@rehivetech.com>

There is a small error in this patch:

2016-07-04 17:16, Jan Viktorin:
> The pci_vfio_has_supported_extensions is not PCI-specific and it is a private
> function of the eal_pci_vfio.c. We just rename the function and make it
> available even for non-PCI devices.
|...]
|> --- a/lib/librte_eal/linuxapp/eal/eal_vfio.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_vfio.c
> @@ -62,6 +62,39 @@ vfio_set_iommu_type(int vfio_container_fd) {
>  }
>  
>  int
> +vfio_has_supported_extensions(int vfio_container_fd) {
> +	int ret;
> +	unsigned idx, n_extensions = 0;
> +	for (idx = 0; idx < RTE_DIM(iommu_types); idx++) {
> +		const struct vfio_iommu_type *t = &iommu_types[idx];
> +
> +		ret = ioctl(vfio_container_fd, VFIO_CHECK_EXTENSION,
> +				t->type_id);
> +		if (ret < 0) {
> +			RTE_LOG(ERR, EAL, "  could not get IOMMU type, "
> +				"error %i (%s)\n", errno,
> +				strerror(errno));
> +			close(vfio_container_fd);

lib/librte_eal/linuxapp/eal/eal_vfio.c:77:4: error:
implicit declaration of function ‘close’

It is fixed in patch 8 with "#include <unistd.h>".

  reply	other threads:[~2016-07-10 17:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-04 15:16 [dpdk-dev] [PATCH v3 00/16] Make VFIO support less dependent on PCI 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 [this message]
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 ` [dpdk-dev] [PATCH v3 00/16] Make VFIO support less dependent on PCI Burakov, Anatoly
2016-07-10 18:17 ` 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=2658506.JKWTbPl3g7@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=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).