support vfio platform PMD
cover support vfio platform PMD
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/[email protected]/
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
RFC PATCH 1/7 lib: add helper to read strings from sysfs files
Reading strings from sysfs files is a re-occurring pattern hence add helper for doing that.
--- app/test/test_eal_fs.c | 108 ++++++++++++++++++++++++++++---- lib/eal/common/eal_filesystem.h | 6 ++ lib/eal/unix/eal_filesystem.c | 24 ++++--- lib/eal/version.map | 3 + 4 files changed, 123 insertions(+), 18 deletions(-)
app/test/test_eal_fs.c +97 -11
@@ -20,12 +20,33 @@ test_eal_fs(void)#else +static int +temp_create (char *filename,size_t len) +{ +char file_template[] ="/tmp/eal_test_XXXXXX" ; +char proc_path[PATH_MAX ]; +int fd; + + fd =mkstemp (file_template); +if (fd ==-1 ) { +perror ("mkstemp() failure" ); +return -1 ; + } + +snprintf (proc_path,sizeof (proc_path),"/proc/self/fd/%d" , fd); +if (readlink (proc_path, filename, len) <0 ) { +perror ("readlink() failure" ); +close (fd); +return -1 ; + } + +return fd; +} +static int test_parse_sysfs_value (void ) {char filename[PATH_MAX ] ="" ; -char proc_path[PATH_MAX ]; -char file_template[] ="/tmp/eal_test_XXXXXX" ;int tmp_file_handle =-1 ;FILE *fd =NULL ;unsigned valid_number;
@@ -40,16 +61,10 @@ test_parse_sysfs_value(void)/* get a temporary filename to use for all tests - create temp file handle and then * use /proc to get the actual file that we can open */ - tmp_file_handle =mkstemp (file_template); -if (tmp_file_handle ==-1 ) { -perror ("mkstemp() failure" ); + tmp_file_handle =temp_create (filename,sizeof (filename)); +if (tmp_file_handle <0 ) goto error; - } -snprintf (proc_path,sizeof (proc_path),"/proc/self/fd/%d" , tmp_file_handle); -if (readlink (proc_path, filename,sizeof (filename)) <0 ) { -perror ("readlink() failure" ); - goto error; - } +printf ("Temporary file is: %s\n" , filename);/* test we get an error value if we use file before it's created */
@@ -175,11 +190,82 @@ test_parse_sysfs_value(void)return -1 ; } +static int +test_parse_sysfs_string (void ) +{ +const char *teststr ="the quick brown dog jumps over the lazy fox\n" ; +char filename[PATH_MAX ] ="" ; +char buf[BUFSIZ ] = { }; +int tmp_file_handle; +FILE *fd =NULL ; + +#ifdef RTE_EXEC_ENV_FREEBSD +/* BSD doesn't have /proc/pid/fd */ +return 0 ; +#endif +printf ("Testing function eal_parse_sysfs_string()\n" ); + +/* get a temporary filename to use for all tests - create temp file handle and then +* use /proc to get the actual file that we can open +*/ + tmp_file_handle =temp_create (filename,sizeof (filename)); +if (tmp_file_handle <0 ) + goto error; + +printf ("Temporary file is: %s\n" , filename); + +/* test we get an error value if we use file before it's created */ +printf ("Test reading a missing file ...\n" ); +if (eal_parse_sysfs_string ("/dev/not-quite-null" , buf,sizeof (buf)) ==0 ) { +printf ("Error with eal_parse_sysfs_string() - returned success on reading empty file\n" ); + goto error; + } +printf ("Confirmed return error when reading empty file\n" ); + +/* test reading a string from file */ +printf ("Test reading string ...\n" ); + fd =fopen (filename,"w" ); +if (fd ==NULL ) { +printf ("line %d, Error opening %s: %s\n" , __LINE__, filename,strerror (errno)); + goto error; + } +fprintf (fd,"%s" , teststr); +fclose (fd); + fd =NULL ; +if (eal_parse_sysfs_string (filename, buf,sizeof (buf) -1 ) <0 ) { +printf ("eal_parse_sysfs_string() returned error - test failed\n" ); + goto error; + } +if (strcmp (teststr, buf)) { +printf ("Invalid string read by eal_parse_sysfs_string() - test failed\n" ); + goto error; + } +/* don't print newline */ + buf[strlen (buf) -1 ] ='\0' ; +printf ("Read '%s\\n' ok\n" , buf); + +close (tmp_file_handle); +unlink (filename); +printf ("eal_parse_sysfs_string() - OK\n" ); +return 0 ; + +error: +if (fd) +fclose (fd); +if (tmp_file_handle >0 ) +close (tmp_file_handle); +if (filename[0 ] !='\0' ) +unlink (filename); +return -1 ; +} +static int test_eal_fs (void ) {if (test_parse_sysfs_value () <0 )return -1 ; +if (test_parse_sysfs_string () <0 ) +return -1 ;return 0 ; }
lib/eal/common/eal_filesystem.h +6 -0
@@ -104,4 +104,10 @@ eal_get_hugefile_path(char *buffer, size_t buflen, const char *hugedir, int f_id* Used to read information from files on /sys */ int eal_parse_sysfs_value (const char *filename,unsigned long *val); +/** Function to read a string from a file on the filesystem. +* Used to read information for files in /sys +*/ +__rte_experimental +int eal_parse_sysfs_string(const char *filename, char *str, size_t size); +#endif /* EAL_FILESYSTEM_H */
lib/eal/unix/eal_filesystem.c +17 -7
@@ -76,12 +76,9 @@ int eal_create_runtime_dir(void)return 0 ; } -/* parse a sysfs (or other) file containing one integer value */ -int eal_parse_sysfs_value (const char *filename,unsigned long *val) +int eal_parse_sysfs_string (const char *filename,char *str,size_t size) {FILE *f; -char buf[BUFSIZ ]; -char *end =NULL ;if ((f =fopen (filename,"r" )) ==NULL ) { RTE_LOG(ERR, EAL, "%s(): cannot open sysfs value %s\n",
@@ -89,19 +86,32 @@ int eal_parse_sysfs_value(const char *filename, unsigned long *val)return -1 ; } -if (fgets (buf,sizeof (buf), f) ==NULL ) { +if (fgets (str, size, f) ==NULL ) {RTE_LOG (ERR ,EAL ,"%s(): cannot read sysfs value %s\n" , __func__, filename);fclose (f);return -1 ; } +fclose (f); +return 0 ; +} + +/* parse a sysfs (or other) file containing one integer value */ +int eal_parse_sysfs_value (const char *filename,unsigned long *val) +{ +char buf[BUFSIZ ]; +char *end =NULL ; +int ret; + + ret =eal_parse_sysfs_string (filename, buf,sizeof (buf)); +if (ret <0 ) +return ret; + *val =strtoul (buf, &end,0 );if ((buf[0 ] =='\0' ) || (end ==NULL ) || (*end !='\n' )) {RTE_LOG (ERR ,EAL ,"%s(): cannot parse sysfs value %s\n" , __func__, filename); -fclose (f);return -1 ; } -fclose (f);return 0 ; }
lib/eal/version.map +3 -0
@@ -440,6 +440,9 @@ EXPERIMENTAL { rte_thread_detach; rte_thread_equal; rte_thread_join; + + # added in 23.03 + eal_parse_sysfs_string; # WINDOWS_NO_EXPORT }; INTERNAL {
Signature · 1 line
2.25.1
Re: [RFC PATCH 1/7] lib: add helper to read strings from sysfs files
lib/eal/version.map EXPERIMENTAL { · line 446
Quoted 12 lines · On Fri, 23 Dec 2022 00:24:29 +0100 Tomasz Duszynski <[email protected]>…
lib/eal/version.map +3
-0@@ -440,6 +440,9 @@ EXPERIMENTAL { rte_thread_detach; rte_thread_equal; rte_thread_join; + + # added in 23.03 + eal_parse_sysfs_string; # WINDOWS_NO_EXPORT };
Should be internal not exported as user API.
RE: [EXT] Re: [RFC PATCH 1/7] lib: add helper to read strings from sysfs files
Hi Stephen,
Quoted 13 lines
-----Original Message-----
From: Stephen Hemminger <[email protected]>
Sent: Friday, December 23, 2022 5:40 PM
To: Tomasz Duszynski <[email protected]>
Cc: [email protected]; [email protected]; Jerin Jacob Kollanukkaran <[email protected]>
Subject: [EXT] Re: [RFC PATCH 1/7] lib: add helper to read strings from sysfs filesExternal Email
----------------------------------------------------------------------
On Fri, 23 Dec 2022 00:24:29 +0100
Tomasz Duszynski <[email protected]> wrote:
Quoted 14 lines
lib/eal/version.map EXPERIMENTAL { · line 446
Quoted 12 lines
lib/eal/version.map index renamed from lib/eal/version.map +0
-0
7ad12a7dc9..2dbc10e6be100644lib/eal/version.map +3
-0@@ -440,6 +440,9 @@ EXPERIMENTAL { rte_thread_detach; rte_thread_equal; rte_thread_join; + + # added in 23.03 + eal_parse_sysfs_string; # WINDOWS_NO_EXPORT };Should be internal not exported as user API.
Okay. I'll put that under different section.
RFC PATCH 2/7 raw/vfio_platform: add driver skeleton
In reply to Tomasz DuszynskiAdd driver skeleton which does not do anything beyond registering driver itself to platform bus and providing means to create and destroy VFIO container.
--- 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 | 49 +++++++++++ drivers/raw/vfio_platform/version.map | 10 +++ drivers/raw/vfio_platform/vfio_platform.c | 85 +++++++++++++++++++ 7 files changed, 186 insertions(+) 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
doc/guides/rawdevs/index.rst +1 -0
@@ -16,3 +16,4 @@ application through rawdev API. dpaa2_cmdif ifpga ntb + vfio_platform
doc/guides/rawdevs/vfio_platform.rst new file +24 -0
@@ -0,0 +1,24 @@ +.. SPDX-License-Identifier: BSD-3-Clause + Copyright(c) 2023 Marvell. + +VFIO Platform driver +==================== + +VFIO platform driver allows to configure and manage kernel VFIO platform devices. +These devices do not normally have built-in bus discovery capabilities, known +for example from PCI bus, and reside behind an IOMMU. + +Features +-------- + +Following features are available: + +- bind to devices managed by kernel vfio-platform driver +- expose device memory resources +- map/unmap DMA memory + +Requirements +------------ + +Since PMD is backed by vfio and vfio-platform kernel drivers they need to be enabled +in kernel config.
drivers/raw/meson.build +1 -0
@@ -12,5 +12,6 @@ drivers = [ 'ifpga', 'ntb', 'skeleton', + 'vfio_platform', ] std_deps = ['rawdev']
drivers/raw/vfio_platform/meson.build new file +16 -0
@@ -0,0 +1,16 @@ +# SPDX-License-Identifier: BSD-3-Clause +# Copyright(C) 2023 Marvell. +# + +if not is_linux + build = false + reason = 'only supported on Linux' +endif + +deps += ['bus_platform', 'rawdev'] +sources = files( + 'vfio_platform.c', +) +headers = files( + 'rte_pmd_vfio_platform.h', +)
drivers/raw/vfio_platform/rte_pmd_vfio_platform.h new file +49 -0
49 lines not on this page · raw message
drivers/raw/vfio_platform/version.map new file +10 -0
@@ -0,0 +1,10 @@ +DPDK_23 { + local: *; +}; + +EXPERIMENTAL { + global: + + rte_pmd_vfio_platform_container_create; + rte_pmd_vfio_platform_container_destroy; +};
drivers/raw/vfio_platform/vfio_platform.c new file +85 -0
85 lines not on this page · raw message
Signature · 1 line
2.25.1
RFC PATCH 3/7 raw/vfio_platform: add platform probe and remove
In reply to Tomasz DuszynskiAdd platform bus probe and remove.
--- drivers/raw/vfio_platform/vfio_platform.c | 56 +++++++++++++++++++++++ drivers/raw/vfio_platform/vfio_platform.h | 35 ++++++++++++++ 2 files changed, 91 insertions(+) create mode 100644 drivers/raw/vfio_platform/vfio_platform.h
drivers/raw/vfio_platform/vfio_platform.c +56 -0
@@ -9,9 +9,14 @@#include <rte_config.h> #include <rte_dev.h> #include <rte_errno.h> +#include <rte_log.h> #include <rte_pmd_vfio_platform.h> +#include <rte_rawdev.h> +#include <rte_rawdev_pmd.h> #include <rte_vfio.h> +#include "vfio_platform.h" + static struct { int container_fd; int refcnt;
@@ -77,9 +82,60 @@ rte_pmd_vfio_platform_container_destroy(int container)return 0 ; } +static const struct rte_rawdev_ops vfio_platform_rawdev_ops = { +}; + +static int +vfio_platform_probe (struct rte_platform_device *pdev) +{ +struct rte_platform_driver *pdrv = pdev->driver; +struct vfio_platform *plat; +struct rte_rawdev *rawdev; + +if (rte_eal_process_type () !=RTE_PROC_PRIMARY ) +return 0 ; + + rawdev =rte_rawdev_pmd_allocate (pdev->device.name,sizeof (*plat),rte_socket_id ()); +if (!rawdev) +return -ENOMEM ; + + rawdev->dev_ops = &vfio_platform_rawdev_ops; + rawdev->device = &pdev->device; + rawdev->driver_name = pdrv->driver.name; + + plat = rawdev->dev_private; + plat->device = pdev; + + pdev->driver_data = plat; + +VFIO_PLATFORM_LOG (INFO ,"probed %s\n" , pdev->device.name); + +return 0 ; +} + +static int +vfio_platform_remove (struct rte_platform_device *pdev) +{ +struct rte_rawdev *rawdev; +int ret; + + rawdev =rte_rawdev_pmd_get_named_dev (pdev->device.name); +if (!rawdev) +return -ENODEV ; + + ret =rte_rawdev_pmd_release (rawdev); +if (ret ==0 ) +VFIO_PLATFORM_LOG (INFO ,"removed %s\n" , pdev->device.name); + +return ret; +} +static struct rte_platform_driver vfio_platform = { + .probe = vfio_platform_probe, + .remove = vfio_platform_remove, };RTE_PMD_REGISTER_PLATFORM (vfio_platform, vfio_platform);RTE_PMD_REGISTER_ALIAS (vfio_platform, vfio-platform);RTE_PMD_REGISTER_KMOD_DEP (vfio_platform,"vfio-platform" ); +RTE_LOG_REGISTER_DEFAULT (vfio_platform_logtype,NOTICE );
drivers/raw/vfio_platform/vfio_platform.h new file +35 -0
@@ -0,0 +1,35 @@ +/* SPDX-License-Identifier: BSD-3-Clause +* Copyright(C) 2023 Marvell. +*/ + +#ifndef _VFIO_PLATFORM_H_ +#define _VFIO_PLATFORM_H_ + +#include <rte_bus_platform.h> +#include <rte_common.h> +#include <rte_dev.h> +#include <rte_log.h> + +extern int vfio_platform_logtype; + +#define VFIO_PLATFORM_LOG (level, ...) \ + rte_log(RTE_LOG_ ## level, vfio_platform_logtype, \ + RTE_FMT("vfio platform: " RTE_FMT_HEAD(__VA_ARGS__,) "\n", \ + RTE_FMT_TAIL(__VA_ARGS__,))) + +struct vfio_platform_resource { +struct rte_mem_resource mem; +const char *name; +}; + +struct vfio_platform { +int dev_fd; +int group_fd; +int group; +int container; +struct rte_platform_device *device; +struct vfio_platform_resource *resource; +int num_resource; +}; + +#endif /* _VFIO_PLATFORM_H_ */
Signature · 1 line
2.25.1
RFC PATCH 4/7 raw/vfio_platform: support rawdev close
In reply to Tomasz DuszynskiAdd support for closing raw device allocated during platform probe.
--- drivers/raw/vfio_platform/vfio_platform.c | 49 +++++++++++++++++++++++ 1 file changed, 49 insertions(+)
drivers/raw/vfio_platform/vfio_platform.c +49 -0
@@ -3,6 +3,8 @@*/ #include <errno.h> +#include <sys/mman.h> +#include <unistd.h> #include <rte_bus_platform.h> #include <rte_common.h>
@@ -17,6 +19,8 @@#include "vfio_platform.h" +#define VFIO_PLATFORM_SYSFS_BASE "/sys/bus/platform/devices" + static struct { int container_fd; int refcnt;
@@ -52,6 +56,12 @@ container_get(int index) container_tbl[index].refcnt++; } +static int +container_fd (int index) +{ +return container_tbl[index].container_fd; +} +int rte_pmd_vfio_platform_container_create (void ) {
@@ -82,7 +92,46 @@ rte_pmd_vfio_platform_container_destroy(int container)return 0 ; } +static void +device_release_maps (struct vfio_platform *plat) +{ +struct vfio_platform_resource *res; +int i; + +for (i =0 ; i < plat->num_resource; i++) { + res = &plat->resource[i]; +munmap (res->mem.addr, res->mem.len); +free ((void *)(size_t )res->name); + } + +free (plat->resource); + plat->resource =NULL ; + plat->num_resource =0 ; +} + +static void +device_release (struct vfio_platform *plat) +{ +device_release_maps (plat); +rte_vfio_release_device (VFIO_PLATFORM_SYSFS_BASE , plat->device->name, plat->dev_fd); +rte_vfio_container_group_unbind (container_fd (plat->container), plat->group); +close (plat->group_fd); +rte_vfio_clear_group (plat->group_fd); +container_put (plat->container); +} + +static int +vfio_rawdev_dev_close (struct rte_rawdev *dev) +{ +struct vfio_platform *plat = dev->dev_private; + +device_release (plat); + +return 0 ; +} +static const struct rte_rawdev_ops vfio_platform_rawdev_ops = { + .dev_close = vfio_rawdev_dev_close, }; static int
Signature · 1 line
2.25.1
RFC PATCH 5/7 raw/vfio_platform: support rawdev configure
In reply to Tomasz DuszynskiAdd support for binding device VFIO group to a VFIO container.
--- .../raw/vfio_platform/rte_pmd_vfio_platform.h | 6 + drivers/raw/vfio_platform/vfio_platform.c | 147 ++++++++++++++++++ 2 files changed, 153 insertions(+)
drivers/raw/vfio_platform/rte_pmd_vfio_platform.h +6 -0
@@ -17,6 +17,12 @@extern "C" {#endif +/** vfio platform device configuration */ +struct vfio_platform_dev_config { +/** logical value representing the vfio container */ +int container; +}; +/** * Create a new VFIO container. *
drivers/raw/vfio_platform/vfio_platform.c +147 -0
180 lines not on this page · raw message
Signature · 1 line
2.25.1
RFC PATCH 6/7 raw/vfio_platform: support rawdev device info
In reply to Tomasz DuszynskiAdd support for querying rawdev device info.
--- .../raw/vfio_platform/rte_pmd_vfio_platform.h | 34 ++++++++++++++ drivers/raw/vfio_platform/vfio_platform.c | 45 +++++++++++++++++++ 2 files changed, 79 insertions(+)
drivers/raw/vfio_platform/rte_pmd_vfio_platform.h +34 -0
@@ -17,6 +17,40 @@ extern "C" { #endif +#include <rte_compat.h> +#include <rte_dev.h> + +/** + * vfio platform device region info + * + * Caller uses that to retrieve information about device memory regions. + * Caller provides either resource name or an index, both of which can + * be extracted from the device tree. The former is equivalent to + * 'reg-names' property while the latter is a 0-based index into 'reg' + * array. + */ +struct vfio_platform_dev_region_info { + /**< mmapped memory resource */ + struct rte_mem_resource mem; + /**< name of the resource */ + const char *name; + /**< index of the resource */ + int index; +}; + +enum vfio_platform_info { + INFO_REGION_INDEX, + INFO_REGION_NAME, +}; + +/**< vfio platform device info */ +struct vfio_platform_dev_info { + /**< Type of device info */ + enum vfio_platform_info type; + /**< Memory region info */ + struct vfio_platform_dev_region_info reg_info; +}; + /** vfio platform device configuration */ struct vfio_platform_dev_config { /** logical value representing the vfio container */
drivers/raw/vfio_platform/vfio_platform.c +45 -0
57 lines not on this page · raw message
Signature · 1 line
2.25.1
RFC PATCH 7/7 raw/vfio_platform: support DMA map/unmap
In reply to Tomasz DuszynskiAdd support for DMA map/unmap operations.
--- .../raw/vfio_platform/rte_pmd_vfio_platform.h | 40 +++++++++++ drivers/raw/vfio_platform/version.map | 2 + drivers/raw/vfio_platform/vfio_platform.c | 67 +++++++++++++++++++ 3 files changed, 109 insertions(+)
drivers/raw/vfio_platform/rte_pmd_vfio_platform.h +40 -0
@@ -82,6 +82,46 @@ __rte_experimentalint rte_pmd_vfio_platform_container_destroy (int container); +/** +* Map DMA memory. +* +* @param dev_id +* Device identifier. +* @param addr +* Virtual address to map. +* @param iova +* IOVA address to map. +* @param len +* Length of the memory segment being mapped. +* +* @return +* 0 on success +* <0 on failure and rte_errno is set +*/ +__rte_experimental +int +rte_pmd_vfio_platform_dma_map (uint16_t dev_id,void *addr,uint64_t iova,size_t len); + +/** +* Remove DMA memory mapping. +* +* @param dev_id +* Device identifier. +* @param addr +* Virtual address to map. +* @param iova +* IOVA address to map. +* @param len +* Length of the memory segment being mapped. +* +* @return +* 0 on success +* <0 on failure and rte_errno is set +*/ +__rte_experimental +int +rte_pmd_vfio_platform_dma_unmap (uint16_t dev_id,void *addr,uint64_t iova,size_t len); + #ifdef __cplusplus }#endif
drivers/raw/vfio_platform/version.map +2 -0
@@ -7,4 +7,6 @@ EXPERIMENTAL { rte_pmd_vfio_platform_container_create; rte_pmd_vfio_platform_container_destroy; + rte_pmd_vfio_platform_dma_map; + rte_pmd_vfio_platform_dma_unmap; };
drivers/raw/vfio_platform/vfio_platform.c +67 -0
82 lines not on this page · raw message
Signature · 1 line
2.25.1
Quoted 23 lines
-----Original Message-----
From: Tomasz Duszynski <[email protected]>
Sent: Friday, December 23, 2022 7:24 AM
To: [email protected]
Cc: [email protected]; [email protected]; Tomasz Duszynski <[email protected]>
Subject: [RFC PATCH 0/7] support vfio platform PMDThis 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.
Quoted 4 lines
PMD requires platform bus support [1].
[1] https://lore.kernel.org/dpdk-dev/20221222000106.270619-1-
[email protected]/
I have not looked into all details. But just wondering: why not making this part of the platform bus. This seems generic and then vendors can have their own platform drivers.
Thanks,
Chenbo
Hi Chenbo,
Quoted 40 lines
-----Original Message-----
From: Xia, Chenbo <[email protected]>
Sent: Friday, December 23, 2022 8:05 AM
To: Tomasz Duszynski <[email protected]>; [email protected]
Cc: [email protected]; Jerin Jacob Kollanukkaran <[email protected]>
Subject: [EXT] RE: [RFC PATCH 0/7] support vfio platform PMDExternal Email
----------------------------------------------------------------------
Quoted 22 lines
-----Original Message-----
From: Tomasz Duszynski <[email protected]>
Sent: Friday, December 23, 2022 7:24 AM
To: [email protected]
Cc: [email protected]; [email protected]; Tomasz Duszynski <[email protected]>
Subject: [RFC PATCH 0/7] support vfio platform PMDThis 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].
Quoted 7 lines
[1]
https://urldefense.proofpoint.com/v2/url?u=https-3A__lore.kernel.org_d
pdk-2Ddev_20221222000106.270619-2D1-2D&d=DwIFAg&c=nKjWec2b6R0mOyPaz7xt fQ&r=PZNXgrbjdlXxVEEGYkxIxRndyEUwWU_ad5ce22YI6Is&m=D9rwjUu4gMDK-DA_YvF eU6OBKRUXqZVQ7Nfg3O4xldhUMqQsXQx4AM9La3PpF1Bd&s=L93CKF1oLmgSm7z50nWbVf 4FFDww_noCSxOENlbfXGY&e=
[email protected]/
Quoted 3 lines
I have not looked into all details. But just wondering: why not making this part of the platform bus. This seems generic and then vendors can have their own platform drivers.
Valid point. I'll rethink current approach.
Quoted 2 lines
Thanks,
Chenbo