From: "Gavin Hu (Arm Technology China)" <Gavin.Hu@arm.com>
To: "Tone Zhang (Arm Technology China)" <Tone.Zhang@arm.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: nd <nd@arm.com>
Subject: Re: [dpdk-dev] [PATCH] doc: Clarify IOMMU usage with "uio-pci" kernel module
Date: Tue, 4 Sep 2018 09:16:41 +0000 [thread overview]
Message-ID: <VI1PR08MB31672A372851F17BEB0498748F030@VI1PR08MB3167.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <1536051547-8797-1-git-send-email-tone.zhang@arm.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of tone.zhang
> Sent: Tuesday, September 4, 2018 4:59 PM
> To: dev@dpdk.org
> Cc: nd <nd@arm.com>
> Subject: [dpdk-dev] [PATCH] doc: Clarify IOMMU usage with "uio-pci" kernel
> module
>
> When binding the devices used by DPDK to the "uio-pci" kernel module, the
> IOMMU should be disabled in order not to break the IO transmission
> because of the virtual / physical address mapping.
>
> The patch clarifies the IOMMU configuration on both x86_64 and arm64
> systems.
>
> Signed-off-by: tone.zhang <tone.zhang@arm.com>
Acked-by: Gavin Hu <gavin.hu@arm.com>
> ---
> doc/guides/linux_gsg/linux_drivers.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/guides/linux_gsg/linux_drivers.rst
> b/doc/guides/linux_gsg/linux_drivers.rst
> index 371a817..8f9ec8f 100644
> --- a/doc/guides/linux_gsg/linux_drivers.rst
> +++ b/doc/guides/linux_gsg/linux_drivers.rst
> @@ -48,6 +48,13 @@ be loaded as shown below:
> ``vfio-pci`` kernel module rather than ``igb_uio`` or ``uio_pci_generic``.
> For more details see :ref:`linux_gsg_binding_kernel` below.
>
> +.. note::
> +
> + If the devices for used DPDK bound to the ``uio-pci`` kernel module, please
> make
> + sure that the IOMMU is disabled. We can add ``intel_iommu=off`` or
> ``amd_iommu=off``
> + in ``GRUB_CMDLINE_LINUX`` in grub on x86_64 systems, or add
> ``iommu.passthrough=1``
> + on arm64 system.
> +
> Since DPDK release 1.7 onward provides VFIO support, use of UIO is optional
> for platforms that support using VFIO.
>
> --
> 2.7.4
next prev parent reply other threads:[~2018-09-04 9:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 8:59 tone.zhang
2018-09-04 9:16 ` Gavin Hu (Arm Technology China) [this message]
2018-09-04 10:06 ` Bruce Richardson
2018-09-04 10:15 ` Luca Boccassi
2018-09-04 10:25 ` Tone Zhang (Arm Technology China)
2018-09-04 19:55 ` Rami Rosen
2018-09-05 0:20 ` Tone Zhang (Arm Technology China)
2018-09-05 9:22 ` Stephen Hemminger
2018-09-05 9:49 ` Tone Zhang (Arm Technology China)
2018-09-05 4:39 ` [dpdk-dev] [PATCH v2] doc: Clarify IOMMU usage with "uio_pci_generic" " tone.zhang
2018-09-05 5:17 ` [dpdk-dev] [PATCH v3] " tone.zhang
2018-09-05 5:23 ` Gavin Hu (Arm Technology China)
2018-09-19 7:44 ` Tone Zhang (Arm Technology China)
2018-09-19 11:33 ` Bruce Richardson
2018-09-19 11:54 ` Luca Boccassi
2018-09-21 2:39 ` Tone Zhang (Arm Technology China)
2018-09-19 10:42 ` Luca Boccassi
2018-09-21 3:07 ` [dpdk-dev] [PATCH v4] " tone.zhang
2018-09-21 11:20 ` Bruce Richardson
2018-09-25 6:18 ` Tone Zhang (Arm Technology China)
2018-09-25 6:54 ` [dpdk-dev] [PATCH v5] " tone.zhang
2018-09-26 5:08 ` [dpdk-dev] [PATCH v6] " tone.zhang
2018-11-19 0:04 ` 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=VI1PR08MB31672A372851F17BEB0498748F030@VI1PR08MB3167.eurprd08.prod.outlook.com \
--to=gavin.hu@arm.com \
--cc=Tone.Zhang@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.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).