All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: luca.boccassi@gmail.com
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] test/debug: fix test failure on ppc64
Date: Fri, 28 Nov 2025 09:54:04 +0100	[thread overview]
Message-ID: <5872466.31r3eYUQgx@thomas> (raw)
In-Reply-To: <aShb5MBcGuyTbb1T@bricha3-mobl1.ger.corp.intel.com>

27/11/2025 15:10, Bruce Richardson:
> On Tue, Nov 25, 2025 at 10:39:13AM +0000, luca.boccassi@gmail.com wrote:
> > From: Luca Boccassi <bluca@debian.org>
> > 
> > 1001s Running binary with argv[]:'/tmp/autopkgtest.LvdXhc/build.6vT/src/build/app/dpdk-test' '--file-prefix=debug' '-l' '0' '--no-huge' '-m' '2048'
> > <...>
> > 1001s EAL: Cannot use IOVA as 'PA' since physical addresses are not available
> > 
> > This is similar to 6b07762e949036389030cf5a1a9bb8a1e4d6ee2d,
> > on ppc64 iova-mode=pa is the default, but it doesn't work with --no-huge,
> > so add --iova-mode=va to the test arguments.
> > 
> > Fixes: 2b403dd8fb37 ("test/debug: fix crash with mlx5 devices")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Luca Boccassi <bluca@debian.org>
> > ---
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>

Applied, thanks.



> > +#ifdef RTE_ARCH_PPC_64
> > +		/* iova=pa is the default, but fails on ppc64 with --no-huge */
> > +		test_args[7] = "--iova-mode=va";
> > +#else
> > +		test_args[7] = "";
> > +#endif
> 
> Next release we should maybe see if we can remove the #ifdefs and just
> iova=va for all architectures.

Yes



      reply	other threads:[~2025-11-28  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25 10:39 [PATCH] test/debug: fix test failure on ppc64 luca.boccassi
2025-11-27 14:10 ` Bruce Richardson
2025-11-28  8:54   ` 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=5872466.31r3eYUQgx@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=luca.boccassi@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.