From: christian.ehrhardt@canonical.com
To: dev <dev@dpdk.org>
Cc: Luca Boccassi <bluca@debian.org>,
David Wilder <dwilder@us.ibm.com>,
Dmitry Kozliuk <dmitry.kozliuk@gmail.com>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [PATCH] test: set iova=va mode on ppc64 with --no-huge
Date: Tue, 28 Nov 2023 15:40:45 +0100 [thread overview]
Message-ID: <20231128144045.2403960-1-christian.ehrhardt@canonical.com> (raw)
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
On ppc64, without huge pages, pa would be the default but fails like:
EAL: Cannot use IOVA as 'PA' since physical addresses are not available
On a normal system setup we'd expect an admin to set up huge pages
and for the unlikely case that they do not do that set iova=va
themselve. But the testing infrastructure does not have this conscious
admin that will do that, so fix test execution that by adjusting the
tests arguments accordingly if the conditions are met.
Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
app/test/suites/meson.build | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/app/test/suites/meson.build b/app/test/suites/meson.build
index 478f245a54..8efbb165bf 100644
--- a/app/test/suites/meson.build
+++ b/app/test/suites/meson.build
@@ -10,6 +10,14 @@ test_no_huge_args = ['--no-huge', '-m', '2048']
has_hugepage = run_command(has_hugepages_cmd, check: true).stdout().strip() != '0'
message('hugepage availability: @0@'.format(has_hugepage))
+# On ppc64, without huge pages, pa would be the default but fails like:
+# EAL: Cannot use IOVA as 'PA' since physical addresses are not available
+if not has_hugepage
+ if arch_subdir == 'ppc'
+ test_no_huge_args += '--iova-mode=va'
+ endif
+endif
+
# process source files to determine the different unit test suites
# - fast_tests
# - perf_tests
--
2.34.1
next reply other threads:[~2023-11-28 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 14:40 christian.ehrhardt [this message]
2023-11-28 14:56 ` Luca Boccassi
2024-03-06 17:50 ` 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=20231128144045.2403960-1-christian.ehrhardt@canonical.com \
--to=christian.ehrhardt@canonical.com \
--cc=--no-chain-reply-to@dpdk.org \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dwilder@us.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).