From: James Bensley <jwbensley@gmail.com>
To: "Johnson, Brian" <brian.johnson@intel.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Hard Crash with X710 and Pktgen
Date: Wed, 15 Nov 2017 17:22:18 +0000 [thread overview]
Message-ID: <CAAWx_pVUK8YmtMFJnRZScSzuP1FZtk3S+BPLs3JN=tRBMYJhGg@mail.gmail.com> (raw)
In-Reply-To: <FC4CB3BF-5564-451E-8309-9CD982B85E3E@intel.com>
On 14 November 2017 at 10:59, Johnson, Brian <brian.johnson@intel.com> wrote:
> Do you have Intel VT-d enabled in the BIOS and intel_iommu=on iommu=pt in
> grub?
...
> Once the system boots up, check the contents of /sys/kernel/iommu_groups/
> directory. If it is non-empty, you have successfully set up IOMMU.
Hi Brian,
Many thanks for your response!
$ ls /sys/kernel/iommu_groups/
0 1 10 11 12 13 14 15 16 17 18 19 2 20 21 22 23 24
25 26 27 28 29 3 30 31 32 33 34 35 36 37 38 39 4 40
41 5 6 7 8 9
There is "stuff" in there so, looks good to me.
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.13.12-1.el7.elrepo.x86_64
root=UUID=e5b08dc0-3ea6-4259-82ab-820dee91fa52 ro intel_pstate=disable
iommu=pt intel_iommu=on default_hugepagesz=1G hugepagesz=1G
hugepages=4 crashkernel=auto rhgb quiet
$ dmesg | grep -i IOMMU
[ 0.000000] DMAR: IOMMU enabled
VT-x is enabled:
$ grep -m 1 -o "vmx" /proc/cpuinfo
vmx
VT-d is enabled:
$ dmesg | grep -i DMAR
[ 0.000000] DMAR: IOMMU enabled
Cheers,
James.
prev parent reply other threads:[~2017-11-15 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 19:35 James Bensley
2017-11-13 21:49 ` Wiles, Keith
2017-11-14 4:49 ` Muhammad Zain-ul-Abideen
2017-11-14 6:29 ` Rosen, Rami
2017-11-14 8:37 ` James Bensley
2017-11-14 10:59 ` Johnson, Brian
2017-11-14 20:20 ` Wiles, Keith
2017-11-15 17:24 ` James Bensley
2017-11-15 18:04 ` James Bensley
2017-11-15 17:22 ` James Bensley [this message]
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='CAAWx_pVUK8YmtMFJnRZScSzuP1FZtk3S+BPLs3JN=tRBMYJhGg@mail.gmail.com' \
--to=jwbensley@gmail.com \
--cc=brian.johnson@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).