From: "Rosen, Rami" <rami.rosen@intel.com>
To: "Stephen Hemminger" <stephen@networkplumber.org>,
"Martin Drašar" <drasar@ics.muni.cz>
Cc: "Avi Cohen (A)" <avi.cohen@huawei.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 17.05 does not find X510 card
Date: Sat, 23 Jun 2018 13:00:00 +0000 [thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F9672D250D@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <20180621080713.44313c33@xeon-e3>
Hi all,
>Secure boot should work with VFIO. As long as you have an IOMMU,
>VFIO is a much better solution.
Stephen is right; moreover, DPDK documentation says explicitly that
...
"If UEFI secure boot is enabled, the Linux kernel may disallow the use of UIO on the system. Therefore, devices for use by DPDK should be bound to the vfio-pci kernel module rather than igb_uio or uio_pci_generic. For more details see Binding and Unbinding Network Ports to/from the Kernel Modules below."
...
See section 4.1, "UIO", in:
https://doc.dpdk.org/guides/linux_gsg/linux_drivers.html
Regards,
Rami Rosen
next prev parent reply other threads:[~2018-06-23 13:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 8:55 Martin Drašar
2018-06-18 8:56 ` [dpdk-users] DPDK 17.05 does not find X710 card Martin Drašar
2018-06-18 9:54 ` [dpdk-users] DPDK 17.05 does not find X510 card Rosen, Rami
2018-06-18 12:41 ` Martin Drašar
2018-06-18 13:09 ` Rosen, Rami
2018-06-18 13:23 ` Martin Drašar
2018-06-18 13:34 ` Rosen, Rami
2018-06-18 13:43 ` Martin Drašar
2018-06-18 21:35 ` Martin Drašar
2018-06-19 0:21 ` Rosen, Rami
2018-06-19 9:57 ` Martin Drašar
2018-06-19 14:12 ` Martin Drašar
2018-06-21 5:58 ` Avi Cohen (A)
2018-06-21 11:02 ` Martin Drašar
2018-06-21 15:07 ` Stephen Hemminger
2018-06-23 13:00 ` Rosen, Rami [this message]
2018-06-25 8:23 ` Martin Drašar
2018-06-25 9:35 ` Rosen, Rami
2018-07-11 13:47 ` Martin Drašar
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=9B0331B6EBBD0E4684FBFAEDA55776F9672D250D@HASMSX110.ger.corp.intel.com \
--to=rami.rosen@intel.com \
--cc=avi.cohen@huawei.com \
--cc=drasar@ics.muni.cz \
--cc=stephen@networkplumber.org \
--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).