DPDK usage discussions
 help / color / mirror / Atom feed
From: Ido Shamay <idoshamay@gmail.com>
To: ramzahrehman@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Cannot Bind eth0 to vfio-pci Driver
Date: Mon, 10 Dec 2018 11:10:31 +0200	[thread overview]
Message-ID: <CAOXPkJ+ALx_OAb6yc+BBYTUU6jrV2p4qvguvqCMJWc2uYEq2-g@mail.gmail.com> (raw)
In-Reply-To: <CAHaWn+GAejOfA3jXJUdEX7Q2KmKpXC4LfAzNvcSWeDJimpqjQw@mail.gmail.com>

What is lspci output for this device?
Looks like the device isn't supported by vfio-pcio (maybe it's a
bridge or a card-bus).

-22 is EINVAL, and from vfio-pci code the only relevant return of this
error from probe flow looks like:

if (pdev->hdr_type != PCI_HEADER_TYPE_NORMAL)
    return -EINVAL;

On Mon, Dec 10, 2018 at 5:49 AM Ramzah Rehman <ramzahrehman@gmail.com> wrote:
>
> I am trying to bind an interface eth0 to vfio driver. I have made sure
> iommu is enabled in grub and kernel. I have loaded the module vfio-pci. Ran
> following commands
>
> #modprobe vfio-pci
> #chmod a+x /dev/vfio
> #chmod 0666 /dev/vfio/*
> #export DPDK_DIR=/usr/src/dpdk-stable-17.11.4
> #sudo $DPDK_DIR/usertools/dpdk-devbind.py --bind=vfio-pci 02:01.0
>
> I got following error:
>
> Error: bind failed for 0000:02:01.0 - Cannot bind to driver vfio-pci
>
> I checked the error in dmesg:
>
> Got :
>
> [ 1815.793823] vfio-pci: probe of 0000:02:01.0 failed with error -22
>
> let me know the reason.
>
> Best Regards,
> Ramzah Rehman



-- 
Ido

  parent reply	other threads:[~2018-12-10  9:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-10  3:49 Ramzah Rehman
2018-12-10  5:28 ` Murali Krishna
2018-12-10  9:10 ` Ido Shamay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-06  5:41 Ramzah Rehman
2018-12-11 16:20 ` Stephen Hemminger

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=CAOXPkJ+ALx_OAb6yc+BBYTUU6jrV2p4qvguvqCMJWc2uYEq2-g@mail.gmail.com \
    --to=idoshamay@gmail.com \
    --cc=ramzahrehman@gmail.com \
    --cc=users@dpdk.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).