From: christian.ehrhardt@canonical.com
To: dev <dev@dpdk.org>
Cc: Luca Boccassi <bluca@debian.org>,
Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: [PATCH 0/1] rebase iova fixes
Date: Thu, 23 Nov 2023 16:51:48 +0100 [thread overview]
Message-ID: <20231123155149.306556-1-christian.ehrhardt@canonical.com> (raw)
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Testing 23.11 has shown that [1] is still needed, all tests
on ppc64 with no-huge still fail due to iova=pa breaking without
pa being available.
This is the rebase of [1] to 23.11 and I've added the matching
change to the documentation as well.
David Wilder (1):
eal/linux: force iova-mode va without pa available
doc/guides/prog_guide/env_abstraction_layer.rst | 9 ++++++---
lib/eal/linux/eal.c | 14 ++++++++------
2 files changed, 14 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2023-11-23 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 15:51 christian.ehrhardt [this message]
2023-11-23 15:51 ` [PATCH 1/1] eal/linux: force iova-mode va without pa available christian.ehrhardt
2023-11-24 6:29 ` Christian Ehrhardt
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=20231123155149.306556-1-christian.ehrhardt@canonical.com \
--to=christian.ehrhardt@canonical.com \
--cc=bluca@debian.org \
--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 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).