From: Tomasz Duszynski <tduszynski@marvell.com>
To: <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <jerinj@marvell.com>,
Tomasz Duszynski <tduszynski@marvell.com>
Subject: [RFC PATCH 0/7] support vfio platform PMD
Date: Fri, 23 Dec 2022 00:24:28 +0100 [thread overview]
Message-ID: <20221222232436.643514-1-tduszynski@marvell.com> (raw)
This series aims to add support for managing vfio platform
devices from userspace application conveniently i.e
without going through the configuration required by vfio
and opencoding everything. Instead convenience helpers
are provided.
vfio platform devices, from the kernel standpoint, are ones
that do not have built-in discovery capabilities and are
behind an IOMMU.
This PMD is backed by both vfio-platform and vfio
kernel drivers and ideally should give access to all
vfio capabilities. As of now, access to memory maps and
DMA are supported.
PMD requires platform bus support [1].
[1] https://lore.kernel.org/dpdk-dev/20221222000106.270619-1-tduszynski@marvell.com/
Tomasz Duszynski (7):
lib: add helper to read strings from sysfs files
raw/vfio_platform: add driver skeleton
raw/vfio_platform: add platform probe and remove
raw/vfio_platform: support rawdev close
raw/vfio_platform: support rawdev configure
raw/vfio_platform: support rawdev device info
raw/vfio_platform: support DMA map/unmap
app/test/test_eal_fs.c | 108 ++++-
doc/guides/rawdevs/index.rst | 1 +
doc/guides/rawdevs/vfio_platform.rst | 24 +
drivers/raw/meson.build | 1 +
drivers/raw/vfio_platform/meson.build | 16 +
.../raw/vfio_platform/rte_pmd_vfio_platform.h | 129 +++++
drivers/raw/vfio_platform/version.map | 12 +
drivers/raw/vfio_platform/vfio_platform.c | 449 ++++++++++++++++++
drivers/raw/vfio_platform/vfio_platform.h | 35 ++
lib/eal/common/eal_filesystem.h | 6 +
lib/eal/unix/eal_filesystem.c | 24 +-
lib/eal/version.map | 3 +
12 files changed, 790 insertions(+), 18 deletions(-)
create mode 100644 doc/guides/rawdevs/vfio_platform.rst
create mode 100644 drivers/raw/vfio_platform/meson.build
create mode 100644 drivers/raw/vfio_platform/rte_pmd_vfio_platform.h
create mode 100644 drivers/raw/vfio_platform/version.map
create mode 100644 drivers/raw/vfio_platform/vfio_platform.c
create mode 100644 drivers/raw/vfio_platform/vfio_platform.h
--
2.25.1
next reply other threads:[~2022-12-22 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 23:24 Tomasz Duszynski [this message]
2022-12-22 23:24 ` [RFC PATCH 1/7] lib: add helper to read strings from sysfs files Tomasz Duszynski
2022-12-23 16:40 ` Stephen Hemminger
2023-01-11 18:19 ` [EXT] " Tomasz Duszynski
2022-12-22 23:24 ` [RFC PATCH 2/7] raw/vfio_platform: add driver skeleton Tomasz Duszynski
2022-12-22 23:24 ` [RFC PATCH 3/7] raw/vfio_platform: add platform probe and remove Tomasz Duszynski
2022-12-22 23:24 ` [RFC PATCH 4/7] raw/vfio_platform: support rawdev close Tomasz Duszynski
2022-12-22 23:24 ` [RFC PATCH 5/7] raw/vfio_platform: support rawdev configure Tomasz Duszynski
2022-12-22 23:24 ` [RFC PATCH 6/7] raw/vfio_platform: support rawdev device info Tomasz Duszynski
2022-12-22 23:24 ` [RFC PATCH 7/7] raw/vfio_platform: support DMA map/unmap Tomasz Duszynski
2022-12-23 7:05 ` [RFC PATCH 0/7] support vfio platform PMD Xia, Chenbo
2023-01-12 8:14 ` Tomasz Duszynski
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=20221222232436.643514-1-tduszynski@marvell.com \
--to=tduszynski@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=thomas@monjalon.net \
/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).