DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH] mem: fix DMA mask width sanity check
Date: Wed, 07 Nov 2018 14:43:27 +0100	[thread overview]
Message-ID: <2972511.zAN3OYqJLo@xps> (raw)
In-Reply-To: <f9052a87-4913-6523-b468-4ec6b1d7d3ab@intel.com>

07/11/2018 12:47, Ferruh Yigit:
> On 11/7/2018 10:14 AM, Burakov, Anatoly wrote:
> > On 07-Nov-18 9:44 AM, Alejandro Lucero wrote:
> >> Current code has different max DMA mask width values for 32 and 64
> >> bits systems. IOMMU hardware could report a higher supported width
> >> than current MAX_DMA_MASK_BITS when RTE_ARCH_64 is not defined. This
> >> is actually true with a 32 bits kernel running in a 64 bits server
> >> with IOMMU hardware. This could also be a problem with embedded systems
> >> using an IOMMU designed for 64 bits in a 32 bits system.
> >>
> >> This patch leaves a single max DMA mask width which will make sure the
> >> mask width is within the range for 64 bits variables used for DMA mask.
> >> This also will avoid wrong values because any value higher than
> >> 64 bits is likely wrong.
> >>
> >> Signed-off-by: Alejandro Lucero <alejandro.lucero@netronome.com>
> >> ---
> > 
> > Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
> 
> Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>

Fixes: 223b7f1d5ef6 ("mem: add function for checking memseg IOVA")

Applied, thanks

      reply	other threads:[~2018-11-07 13:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07  9:44 Alejandro Lucero
2018-11-07 10:14 ` Burakov, Anatoly
2018-11-07 11:47   ` Ferruh Yigit
2018-11-07 13:43     ` 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=2972511.zAN3OYqJLo@xps \
    --to=thomas@monjalon.net \
    --cc=alejandro.lucero@netronome.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).