From: Stephen Hemminger <stephen@networkplumber.org>
To: Chaitanya Babu Talluri <tallurix.chaitanya.babu@intel.com>
Cc: dev@dpdk.org, reshma.pattan@intel.com,
jananeex.m.parthasarathy@intel.com, anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH v4 0/4] add unit tests for eal vfio library
Date: Wed, 14 Jun 2023 12:37:07 -0700 [thread overview]
Message-ID: <20230614123707.11b6ca9a@hermes.local> (raw)
In-Reply-To: <1567598682-2225-1-git-send-email-tallurix.chaitanya.babu@intel.com>
On Wed, 4 Sep 2019 13:04:38 +0100
Chaitanya Babu Talluri <tallurix.chaitanya.babu@intel.com> wrote:
> 1/4: fix vfio unmap that fails unexpectedly
> 2/4: fix vfio unmap that succeeds unexpectedly
> 3/4: add API to check iommu type is set
> 4/4: add unit tests for eal vfio
>
> Patch 4/4 depends on 1/4,2/4,3/4
>
> Signed-off-by: Chaitanya Babu Talluri <tallurix.chaitanya.babu@intel.com>
> ---
> v4: Fixed compilation issues.
> v3: Added API to check iommu type.
> v2: Updated commit messages.
> ---
>
> Chaitanya Babu Talluri (4):
> lib/eal: fix vfio unmap that fails unexpectedly
> lib/eal: fix vfio unmap that succeeds unexpectedly
> lib/eal: add API to check iommu type is set
> app/test: add unit tests for eal vfio
>
> app/test/Makefile | 1 +
> app/test/meson.build | 2 +
> app/test/test_eal_vfio.c | 737 +++++++++++++++++++++++
> lib/librte_eal/common/include/rte_vfio.h | 11 +
> lib/librte_eal/linux/eal/eal_vfio.c | 75 ++-
> lib/librte_eal/rte_eal_version.map | 3 +
> 6 files changed, 822 insertions(+), 7 deletions(-)
> create mode 100644 app/test/test_eal_vfio.c
>
This patch series looks OK, but is so out of date that EAL layout
has changed. If still interested, then please rebase on current main branch;
retest and resubmit it.
Thanks
next prev parent reply other threads:[~2023-06-14 19:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 13:02 [dpdk-dev] [PATCH 0/3] " Chaitanya Babu Talluri
2019-08-21 13:02 ` [dpdk-dev] [PATCH 1/3] lib/eal: fix vfio unmap that fails unexpectedly Chaitanya Babu Talluri
2019-08-21 13:20 ` Burakov, Anatoly
2019-08-21 13:02 ` [dpdk-dev] [PATCH 2/3] lib/eal: fix vfio unmap that succeeds unexpectedly Chaitanya Babu Talluri
2019-08-21 13:24 ` Burakov, Anatoly
2019-08-21 13:02 ` [dpdk-dev] [PATCH 3/3] app/test: add unit tests for eal vfio Chaitanya Babu Talluri
2019-08-21 15:44 ` Aaron Conole
2019-08-22 7:18 ` Chaitanya Babu, TalluriX
2019-08-22 10:57 ` Burakov, Anatoly
2019-08-22 14:40 ` Aaron Conole
2019-08-22 11:53 ` [dpdk-dev] [PATCH v2 0/3] add unit tests for eal vfio library Chaitanya Babu Talluri
2019-08-27 11:57 ` [dpdk-dev] [PATCH v3 0/4] " Chaitanya Babu Talluri
2019-09-04 12:04 ` [dpdk-dev] [PATCH v4 " Chaitanya Babu Talluri
2019-09-23 15:56 ` Burakov, Anatoly
2023-06-14 19:37 ` Stephen Hemminger [this message]
2019-09-04 12:04 ` [dpdk-dev] [PATCH v4 1/4] lib/eal: fix vfio unmap that fails unexpectedly Chaitanya Babu Talluri
2019-09-04 12:04 ` [dpdk-dev] [PATCH v4 2/4] lib/eal: fix vfio unmap that succeeds unexpectedly Chaitanya Babu Talluri
2019-09-04 12:04 ` [dpdk-dev] [PATCH v4 3/4] lib/eal: add API to check iommu type is set Chaitanya Babu Talluri
2019-09-04 12:04 ` [dpdk-dev] [PATCH v4 4/4] app/test: add unit tests for eal vfio Chaitanya Babu Talluri
2019-08-27 11:57 ` [dpdk-dev] [PATCH v3 1/4] lib/eal: fix vfio unmap that fails unexpectedly Chaitanya Babu Talluri
2019-08-27 11:57 ` [dpdk-dev] [PATCH v3 2/4] lib/eal: fix vfio unmap that succeeds unexpectedly Chaitanya Babu Talluri
2019-08-27 11:57 ` [dpdk-dev] [PATCH v3 3/4] lib/eal: add API to check iommu type is set Chaitanya Babu Talluri
2019-08-27 11:57 ` [dpdk-dev] [PATCH v3 4/4] app/test: add unit tests for eal vfio Chaitanya Babu Talluri
2019-08-22 11:53 ` [dpdk-dev] [PATCH v2 1/3] lib/eal: fix vfio unmap that fails unexpectedly Chaitanya Babu Talluri
2019-08-22 11:53 ` [dpdk-dev] [PATCH v2 2/3] lib/eal: fix vfio unmap that succeeds unexpectedly Chaitanya Babu Talluri
2019-08-22 11:53 ` [dpdk-dev] [PATCH v2 3/3] app/test: add unit tests for eal vfio Chaitanya Babu Talluri
2019-08-22 12:15 ` Burakov, Anatoly
2019-08-23 7:57 ` Chaitanya Babu, TalluriX
2019-08-23 9:12 ` Burakov, Anatoly
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=20230614123707.11b6ca9a@hermes.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=reshma.pattan@intel.com \
--cc=tallurix.chaitanya.babu@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).