From: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>
To: Sarosh Arif <sarosh.arif@emumba.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] unable to bind to vfio-pci
Date: Thu, 17 Sep 2020 07:31:56 +0000 [thread overview]
Message-ID: <BY5PR11MB3910EFC650D2A1E71B9EB38EED3E0@BY5PR11MB3910.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CABoZmYMNfNAEQ_=-9JWZKPazx+RkeTgs0A_F=cz7OYKd8XQNsA@mail.gmail.com>
Hi.
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Sarosh Arif
> Sent: Thursday, 17 September, 2020 08:53
> To: dev@dpdk.org
> Subject: [dpdk-dev] unable to bind to vfio-pci
>
> I have been trying to bind to vfio-pci using usertools/dpdk-devbind.py but
> am unable to do so. The reason behind this is that I am unable to write in
> /sys/bus/pci/drivers/vfio-pci/bind. Upon searching solutions I tried a couple
> of things such as setting iommu=pt and intel_iommu=on and ensured vt-d is
> enabled.
[Adam] First thing: to check if VT-d is enabled in Linux, you can read MSR 0x3a register. Its lowest bit set will show VT-d works:
(optionally on Ubuntu: apt-get install msr-tools)
modprobe msr
rdmsr 0x3a
3 or 5 -> OK
Other possible way to check for VT-d (IOMMU) working is to view the booting log (dmesg):
dmesg | grep DMAR
"DMAR: IOMMU enabled" -> OK
Both of these should be met in order to use vfio-pci in the next step.
> Along with this I have made sure that the vfio-pci module is correctly loaded.
> I have also tried
>
> chmod 666 /sys/bus/pci/drivers/vfio-pci/bind
>
> So that I have permissions to write in this file.
>
> The error I get when I use usertools/dpdk-devbind.py to bind is this:
> Error: bind failed for 0000:b7:00.1 - Cannot bind to driver vfio-pci
>
> The details of 0000:b7:00.1 are as follows:
> Ethernet Connection X722 for 10GBASE-T 37d2' if=eno6 drv=i40e
>
> I have also unbinded The pci bridge to which 0000:b7:00.1 was connected.
>
> What more can be done to resolve this?
>
> Regards,
> Sarosh Arif
Adam Dybkowski
next prev parent reply other threads:[~2020-09-17 7:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 6:52 Sarosh Arif
2020-09-17 7:31 ` Dybkowski, AdamX [this message]
2020-09-17 8:39 ` Sarosh Arif
2020-09-17 9:17 ` Bruce Richardson
2020-09-17 9:21 ` Sarosh Arif
2020-09-17 9:35 ` Burakov, Anatoly
2020-09-21 11:54 ` Sarosh Arif
2020-09-21 11:58 ` Burakov, Anatoly
2020-09-17 10:22 ` Bruce Richardson
2020-09-17 11:49 ` Burakov, Anatoly
2020-09-21 11:10 ` Sarosh Arif
2020-09-21 11:36 ` Burakov, Anatoly
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=BY5PR11MB3910EFC650D2A1E71B9EB38EED3E0@BY5PR11MB3910.namprd11.prod.outlook.com \
--to=adamx.dybkowski@intel.com \
--cc=dev@dpdk.org \
--cc=sarosh.arif@emumba.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).