DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com, tyos@jp.ibm.com,
	drc@linux.vnet.ibm.com, jerinj@marvell.com
Subject: Re: [dpdk-dev] [PATCH v2] bus/pci: always check IOMMU capabilities
Date: Mon, 05 Aug 2019 12:09:31 +0200	[thread overview]
Message-ID: <10043094.0uuPW0iTYO@xps> (raw)
In-Reply-To: <1564986207-20533-1-git-send-email-david.marchand@redhat.com>

05/08/2019 08:23, David Marchand:
> IOMMU capabilities won't change and must be checked even if no PCI device
> seem to be supported yet when EAL initialised.
> 
> This is to accommodate with SPDK that registers its drivers after
> rte_eal_init(), especially on PPC platform where the IOMMU does not
> support VA.
> 
> Fixes: 703458e19c16 ("bus/pci: consider only usable devices for IOVA mode")
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Reviewed-by: David Christensen <drc@linux.vnet.ibm.com>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
> Tested-by: Jerin Jacob <jerinj@marvell.com>
> Tested-by: Takeshi Yoshimura <tyos@jp.ibm.com>

Applied, thanks




      reply	other threads:[~2019-08-05 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-02 10:14 [dpdk-dev] [PATCH] " David Marchand
2019-08-02 10:20 ` David Marchand
2019-08-02 17:13   ` David Christensen
2019-08-02 17:10 ` David Christensen
2019-08-03 18:22 ` Jerin Jacob Kollanukkaran
2019-08-05  3:57 ` Takeshi T Yoshimura
2019-08-05  6:16   ` David Marchand
2019-08-05  6:23 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-08-05 10:09   ` Thomas Monjalon [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=10043094.0uuPW0iTYO@xps \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=jerinj@marvell.com \
    --cc=tyos@jp.ibm.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).