DPDK patches and discussions
 help / color / mirror / Atom feed
From: "François-Frédéric Ozog" <ff@ozog.com>
To: "'Sridhar S'" <sridhar.nest@gmail.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] Issue when the kernel parameter intel_iommu=on is being	used
Date: Sun, 5 Jan 2014 18:28:47 +0100	[thread overview]
Message-ID: <019901cf0a3b$97b47cd0$c71d7670$@com> (raw)
In-Reply-To: <CAE9sBEAzvGiwb3VVBg+V6xmSpkpzyJ0K5dDFAeS+E4PDo=Z6AA@mail.gmail.com>

Hi,

To understand the issue, you may have a look at:
http://www.intel.com/content/www/us/en/intelligent-systems/intel-technology/
vt-directed-io-spec.html

When you have no IOMMU, "physical" address space is accessed directly by
hardware, so your core works.

When VT-d is active, there is DMA/IRQ remapping hardware layer between the
device and the memory/cpu. If you look at §3.4.3 of the spec, you that for
each device of each bus there is a context (enumerated at boot time,
leveraging BIOS/ACPI). For each device, you may have address translation
programmed so that DMA produced by hardware is actually mapped to a physical
address.

When you use the Linux kernel API for mapping DMA memory, Linux takes care
of the "details". 

For DPDK, documentation §5.6 Using Linux IOMMU Pass-Through to Run Intel®
DPDK with Intel® VT-d says that you should have iommu=pt kernel parameter
on. Do you have it ?

FF


> -----Message d'origine-----
> De : dev [mailto:dev-bounces@dpdk.org] De la part de Sridhar S
> Envoyé : dimanche 5 janvier 2014 13:38
> À : dev@dpdk.org
> Objet : [dpdk-dev] Issue when the kernel parameter intel_iommu=on is being
> used
> 
> Hello,
> 
> 
> 
> I am using DPDK 1.5 for development of host pmd for device “Connect X3”.
> 
> 
> 
> I am observing issue  while the ConnectX3 device DMA to a memory which is
> allocated with rte_memzone_reserve_aligned() API .
> 
> The issue(please refer ERROR below) has been observed if the system runs
> with the kernel parameter “intel_iommu=on”.
> 
> 
> 
> ERROR :
> 
> dmar: DRHD: handling fault status reg 302
> 
> dmar: DMAR:[DMA Write] Request device [01:00.0] fault addr 4f883000
> 
> DMAR:[fault reason 01] Present bit in root entry is clear
> 
> 
> The reported "fault Addr" is the physical address which was returned by
the
> Above API.
> 
> 
> 
> I don’t see any issue with the same code when the system up with kernel
> parameter intel_iommu=off.
> 
> 
> 
> 
> Can you share your comments on this issue?
> 
> 
> Thanks in advance
> 
> Sri

  reply	other threads:[~2014-01-05 17:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-05 12:37 Sridhar S
2014-01-05 17:28 ` François-Frédéric Ozog [this message]
2014-01-06 14:03   ` Sridhar S

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='019901cf0a3b$97b47cd0$c71d7670$@com' \
    --to=ff@ozog.com \
    --cc=dev@dpdk.org \
    --cc=sridhar.nest@gmail.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).