All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>, dev@dpdk.org
Subject: Re: [PATCH v2 3/6] bus/pci: check iommu addressing limitation just once
Date: Fri, 5 Oct 2018 13:16:50 +0100	[thread overview]
Message-ID: <162614ea-0f93-b1fd-cef4-cda55cd78553@intel.com> (raw)
In-Reply-To: <1538741212-7922-4-git-send-email-alejandro.lucero@netronome.com>

On 05-Oct-18 1:06 PM, Alejandro Lucero wrote:
> Current code checks if IOMMU hardware reports enough addressing
> bits for using IOVA mode but it repeats the same check for any
> PCI device present. This is not necessary because the IOMMU hardware
> is the same for all of them.
> 
> This patch only checks the IOMMU using first PCI device found.
> 
> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> ---

Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>

-- 
Thanks,
Anatoly

  reply	other threads:[~2018-10-05 12:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-05 12:06 [PATCH v2 0/6] use IOVAs check based on DMA mask Alejandro Lucero
2018-10-05 12:06 ` [PATCH v2 1/6] mem: add function for checking memsegs IOVAs addresses Alejandro Lucero
2018-10-05 12:15   ` Burakov, Anatoly
2018-10-05 12:19     ` Alejandro Lucero
2018-10-05 12:20       ` Burakov, Anatoly
2018-10-05 12:06 ` [PATCH v2 2/6] mem: use address hint for mapping hugepages Alejandro Lucero
2018-10-05 12:16   ` Burakov, Anatoly
2018-10-05 12:06 ` [PATCH v2 3/6] bus/pci: check iommu addressing limitation just once Alejandro Lucero
2018-10-05 12:16   ` Burakov, Anatoly [this message]
2018-10-05 12:06 ` [PATCH v2 4/6] bus/pci: use IOVAs dmak mask check when setting IOVA mode Alejandro Lucero
2018-10-05 12:18   ` Burakov, Anatoly
2018-10-05 12:06 ` [PATCH v2 5/6] net/nfp: check hugepages IOVAs based on DMA mask Alejandro Lucero
2018-10-05 12:06 ` [PATCH v2 6/6] net/nfp: support IOVA VA mode Alejandro Lucero

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=162614ea-0f93-b1fd-cef4-cda55cd78553@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=alejandro.lucero@netronome.com \
    --cc=dev@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 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.