From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Ravi Kerur <rkerur@gmail.com>
Cc: dev@dpdk.org
Subject: Re: IXGBE, IOMMU DMAR DRHD handling fault issue
Date: Thu, 15 Feb 2018 10:28:33 +0000 [thread overview]
Message-ID: <3b6d6cfc-7e2e-70ee-e059-aa31dc23c93b@intel.com> (raw)
In-Reply-To: <CAFb4SLCBCdmAQPCQWjUm53k6Q82eO0uRN6x9JkeSzqdF0rcRUg@mail.gmail.com>
On 14-Feb-18 8:00 PM, Ravi Kerur wrote:
>
> Earlier I was focusing only on DMAR errors and I might have said 'it
> worked' when I didn't notice them on host when dpdk was started on
> guest. When trying to send packets out of that interface from guest I
> did see DMAR errors. I am attaching information you requested. I have
> enabled log-level=8 and files contain dpdk EAL/PMD logs as well.
Great, now we're on the same page.
>
> Snippets below
>
> on host, DMAR fault address from dmesg
>
> [351576.998109] DMAR: DRHD: handling fault status reg 702
> [351576.998113] DMAR: [DMA Read] Request device [04:10.0] fault addr
> 257617000 [fault reason 06] PTE Read access is not set
>
> on guest (dump phys_mem_layout)
>
> Segment 235: phys:0x257600000, len:2097152, virt:0x7fce87e00000,
> socket_id:0, hugepage_sz:2097152, nchannel:0, nrank:0
> ...
> PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7fce87e0f4c0
> sw_sc_ring=0x7fce87e07380 hw_ring=0x7fce87e17600 dma_addr=0x257617600
> PMD: ixgbe_dev_rx_queue_setup(): sw_ring=0x7fce89c67d40
> sw_sc_ring=0x7fce89c5fc00 hw_ring=0x7fce89c6fe80 dma_addr=0x25406fe80
> ...
>
To me this looks like host (i.e. either QEMU or the PF driver) is trying
to do DMA using guest-physical (and not host-physical). I'm not too
well-versed in how QEMU works, but i'm pretty sure that's not supposed
to happen.
Is PF also bound to DPDK, or are you using native Linux ixgbe driver?
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-02-15 10:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 17:25 IXGBE, IOMMU DMAR DRHD handling fault issue Ravi Kerur
2018-01-24 10:31 ` Burakov, Anatoly
2018-01-24 19:13 ` Ravi Kerur
2018-01-25 10:49 ` Burakov, Anatoly
2018-01-29 22:35 ` Ravi Kerur
2018-01-31 9:59 ` Burakov, Anatoly
2018-01-31 21:51 ` Ravi Kerur
2018-02-01 10:10 ` Burakov, Anatoly
2018-02-01 19:26 ` Ravi Kerur
2018-02-02 10:28 ` Burakov, Anatoly
2018-02-02 20:21 ` Ravi Kerur
2018-02-02 20:51 ` Ravi Kerur
2018-02-05 10:01 ` Burakov, Anatoly
2018-02-06 17:55 ` Ravi Kerur
2018-02-08 11:20 ` Burakov, Anatoly
2018-02-09 17:41 ` Ravi Kerur
2018-02-10 10:11 ` Burakov, Anatoly
2018-02-10 10:58 ` Burakov, Anatoly
2018-02-10 17:53 ` Ravi Kerur
2018-02-12 10:13 ` Burakov, Anatoly
2018-02-12 22:00 ` Ravi Kerur
2018-02-13 14:31 ` Burakov, Anatoly
2018-02-14 20:00 ` Ravi Kerur
2018-02-15 10:28 ` Burakov, Anatoly [this message]
2018-02-15 18:27 ` Ravi Kerur
2018-02-15 20:53 ` Ravi Kerur
2018-02-16 9:41 ` Burakov, Anatoly
2019-01-15 7:07 ` Hu, Xuekun
2019-01-15 11:22 ` Burakov, Anatoly
2019-01-15 13:07 ` Hu, Xuekun
2019-01-21 13:18 ` Hu, Xuekun
2019-01-21 13:39 ` Burakov, Anatoly
2019-01-21 14:44 ` Thomas Monjalon
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=3b6d6cfc-7e2e-70ee-e059-aa31dc23c93b@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=rkerur@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.