From: Masatake YAMATO <yamato@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: yamato@redhat.com, ldv@strace.io, alex.williamson@redhat.com
Subject: [PATCH] vfio: show the name of IOMMU driver in /proc/$pid/fdinfo
Date: Fri, 29 Aug 2025 05:21:00 +0900 [thread overview]
Message-ID: <20250828202100.3661180-1-yamato@redhat.com> (raw)
The ops of VFIO overlap:
(include/uapi/linux/vfio.h)
#define VFIO_DEVICE_GET_PCI_HOT_RESET_INFO _IO(VFIO_TYPE, VFIO_BASE + 12)
...
#define VFIO_MIG_GET_PRECOPY_INFO _IO(VFIO_TYPE, VFIO_BASE + 21)
...
#define VFIO_IOMMU_DIRTY_PAGES _IO(VFIO_TYPE, VFIO_BASE + 17)
#define VFIO_IOMMU_SPAPR_TCE_GET_INFO _IO(VFIO_TYPE, VFIO_BASE + 12)
#define VFIO_EEH_PE_OP _IO(VFIO_TYPE, VFIO_BASE + 21)
#define VFIO_IOMMU_SPAPR_REGISTER_MEMORY _IO(VFIO_TYPE, VFIO_BASE + 17)
...
#define VFIO_IOMMU_SPAPR_TCE_REMOVE _IO(VFIO_TYPE, VFIO_BASE + 20)
These overlapping makes strace decoding the ops and their arguments hard.
See also https://lists.strace.io/pipermail/strace-devel/2021-May/010561.html
This change adds "vfio-iommu-driver" field to /proc/$pid/fdinfo/$fd
where $fd opens /dev/vfio/vfio. The value of the field helps strace
decode the ops arguments.
The prototype version of strace based on this change works fine:
- https://lists.strace.io/pipermail/strace-devel/2021-August/010660.html
- https://lists.strace.io/pipermail/strace-devel/2021-August/010660.html
Cc: Dmitry V. Levin <ldv@strace.io>
Signed-off-by: Masatake YAMATO <yamato@redhat.com>
---
drivers/vfio/container.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/vfio/container.c b/drivers/vfio/container.c
index d53d08f16973..03677fda49de 100644
--- a/drivers/vfio/container.c
+++ b/drivers/vfio/container.c
@@ -11,6 +11,7 @@
#include <linux/iommu.h>
#include <linux/miscdevice.h>
#include <linux/vfio.h>
+#include <linux/seq_file.h>
#include <uapi/linux/vfio.h>
#include "vfio.h"
@@ -384,12 +385,22 @@ static int vfio_fops_release(struct inode *inode, struct file *filep)
return 0;
}
+static void vfio_fops_show_fdinfo(struct seq_file *m, struct file *filep)
+{
+ struct vfio_container *container = filep->private_data;
+ struct vfio_iommu_driver *driver = container->iommu_driver;
+
+ if (driver && driver->ops->name)
+ seq_printf(m, "vfio-iommu-driver:\t%s\n", driver->ops->name);
+}
+
static const struct file_operations vfio_fops = {
.owner = THIS_MODULE,
.open = vfio_fops_open,
.release = vfio_fops_release,
.unlocked_ioctl = vfio_fops_unl_ioctl,
.compat_ioctl = compat_ptr_ioctl,
+ .show_fdinfo = vfio_fops_show_fdinfo,
};
struct vfio_container *vfio_container_from_file(struct file *file)
--
2.51.0
next reply other threads:[~2025-08-28 20:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 20:21 Masatake YAMATO [this message]
2025-08-28 21:44 ` Alex Williamson
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=20250828202100.3661180-1-yamato@redhat.com \
--to=yamato@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=ldv@strace.io \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®