DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] vfio: only map regions VFIO supports
Date: Fri, 10 Jul 2015 07:54:10 +0000	[thread overview]
Message-ID: <533710CFB86FA344BFBF2D6802E60286046B663B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1436395131-11205-1-git-send-email-stephen@networkplumber.org>

Hi, Stephen

This patch does not work for fm10k with vfio, see error below:

EAL: PCI device 0000:84:00.0 on NUMA socket 1
EAL:   probe driver: 8086:15a4 rte_pmd_fm10k
EAL:   PCI memory mapped at 0x7f1980000000
EAL: Trying to map BAR 2 that contains the MSI-X table. Trying offsets:
0000:0000, 1000:1000
EAL:   PCI memory mapped at 0x7f1980401000
EAL: pci_map_resource(): cannot mmap(105, 0x7f1980402000, 0x4000000,
0x0): Invalid argument (0xffffffffffffffff)
EAL:   0000:84:00.0 mapping BAR4 failed: Invalid argument
EAL: Error - exiting with code: 1
  Cause: Requested device 0000:84:00.0 cannot be used


Thanks,
Michael

On 7/9/2015 6:39 AM, Stephen Hemminger wrote:
> The FM10K driver has 3 BARS numbered 0, 4, and 8. But the kernel
> VFIO driver only allows mapping 0-5 anything bigger than that will
> return -EINVAL (see kernel source vfio_pci.c:vfio_pci_mmap).
>
> The workaround is to limit the DPDK EAL VFIO support only map
> the regions that will work. The FM10K driver is not using BAR8
> in current code anyway.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>  lib/librte_eal/linuxapp/eal/eal_pci_vfio.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
> index 426953a..e269e75 100644
> --- a/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
> +++ b/lib/librte_eal/linuxapp/eal/eal_pci_vfio.c
> @@ -549,7 +549,7 @@ pci_vfio_map_resource(struct rte_pci_device *dev)
>  	int iommu_group_no;
>  	char pci_addr[PATH_MAX] = {0};
>  	struct rte_pci_addr *loc = &dev->addr;
> -	int i, ret, msix_bar;
> +	int i, ret, msix_bar, nmaps;
>  	struct mapped_pci_resource *vfio_res = NULL;
>  	struct mapped_pci_res_list *vfio_res_list = RTE_TAILQ_CAST(rte_vfio_tailq.head, mapped_pci_res_list);
>  
> @@ -724,7 +724,9 @@ pci_vfio_map_resource(struct rte_pci_device *dev)
>  	/* map BARs */
>  	maps = vfio_res->maps;
>  
> -	for (i = 0; i < (int) vfio_res->nb_maps; i++) {
> +	/* VFIO supports limited (0-5) maps */
> +	nmaps = RTE_MIN(vfio_res->nb_maps, VFIO_PCI_ROM_REGION_INDEX - 1);
> +	for (i = 0; i < nmaps; i++) {
>  		struct vfio_region_info reg = { .argsz = sizeof(reg) };
>  		void *bar_addr;
>  		struct memreg {


  reply	other threads:[~2015-07-10  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 22:38 Stephen Hemminger
2015-07-10  7:54 ` Qiu, Michael [this message]
2015-07-10 17:24   ` Stephen Hemminger
2015-07-14 10:45     ` Qiu, Michael
2015-07-14 11:03     ` Qiu, Michael

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=533710CFB86FA344BFBF2D6802E60286046B663B@SHSMSX101.ccr.corp.intel.com \
    --to=michael.qiu@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).