From: "Martin Drašar" <drasar@ics.muni.cz>
To: "Avi Cohen (A)" <avi.cohen@huawei.com>,
"Rosen, Rami" <rami.rosen@intel.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK 17.05 does not find X510 card
Date: Thu, 21 Jun 2018 13:02:34 +0200 [thread overview]
Message-ID: <d24d9bf3-f7d0-8751-cf27-348016d3ae6c@ics.muni.cz> (raw)
In-Reply-To: <B84047ECBD981D4B93EAE5A6245AA361015BB23E@FRAEML521-MBX.china.huawei.com>
Dne 21.6.2018 v 7:58 Avi Cohen (A) napsal(a):
> Look at this
> https://stackoverflow.com/questions/8213671/mmap-operation-not-permitted
Hello Avi,
thank you for chiming in. Neither iomem runtime parameter or allowing
mmap on 0 page helped me. As for the latter, DPDK correctly maps to PCI
region, so that is not the problem.
Looking at the mmap source, there are basically only two points that
result in EPERM error. First one is related to incorrect flag
combination (not a DPDK case) the second is related to the file
descriptor of the resource being locked (should not be, but it is the
only possibility).
That lock may have to do something with Secure boot being on, as almost
the same system without secure boot is working ok. I built a custom
kernel with CONFIG_STRICT_DEVMEM turned off, but it's going to take me
some time to hammer it into the system, mainly because I am leaving for
a vacation today.
But it would be great if anyone, who has experience running DPDK on
secure booted systems, could share their experience.
Cheers,
Martin
next prev parent reply other threads:[~2018-06-21 11:02 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 [this message]
2018-06-21 15:07 ` Stephen Hemminger
2018-06-23 13:00 ` Rosen, Rami
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=d24d9bf3-f7d0-8751-cf27-348016d3ae6c@ics.muni.cz \
--to=drasar@ics.muni.cz \
--cc=avi.cohen@huawei.com \
--cc=rami.rosen@intel.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).