From: Jason Gunthorpe <jgg@nvidia.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, ajones@ventanamicro.com,
yan.y.zhao@intel.com, kevin.tian@intel.com, peterx@redhat.com
Subject: Re: [PATCH 1/2] vfio: Create vfio_fs_type with inode per device
Date: Fri, 24 May 2024 10:24:33 -0300 [thread overview]
Message-ID: <20240524132433.GW20229@nvidia.com> (raw)
In-Reply-To: <20240523195629.218043-2-alex.williamson@redhat.com>
On Thu, May 23, 2024 at 01:56:26PM -0600, Alex Williamson wrote:
> By linking all the device fds we provide to userspace to an
> address space through a new pseudo fs, we can use tools like
> unmap_mapping_range() to zap all vmas associated with a device.
>
> Suggested-by: Jason Gunthorpe <jgg@nvidia.com>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
> ---
> drivers/vfio/device_cdev.c | 7 ++++++
> drivers/vfio/group.c | 7 ++++++
> drivers/vfio/vfio_main.c | 44 ++++++++++++++++++++++++++++++++++++++
> include/linux/vfio.h | 1 +
> 4 files changed, 59 insertions(+)
Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Jason
next prev parent reply other threads:[~2024-05-24 13:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 19:56 [PATCH 0/2] vfio/pci: vfio device address space mapping Alex Williamson
2024-05-23 19:56 ` [PATCH 1/2] vfio: Create vfio_fs_type with inode per device Alex Williamson
2024-05-24 13:24 ` Jason Gunthorpe [this message]
2024-05-29 23:59 ` Tian, Kevin
2024-05-23 19:56 ` [PATCH 2/2] vfio/pci: Use unmap_mapping_range() Alex Williamson
2024-05-24 0:39 ` Yan Zhao
2024-05-24 0:49 ` Peter Xu
2024-05-24 1:47 ` Yan Zhao
2024-05-28 18:42 ` Alex Williamson
2024-05-29 2:29 ` Yan Zhao
2024-05-29 3:12 ` Alex Williamson
2024-05-29 6:34 ` Yan Zhao
2024-05-29 16:50 ` Alex Williamson
2024-05-30 7:46 ` Yan Zhao
2024-05-24 8:40 ` Tian, Kevin
2024-05-24 13:22 ` Jason Gunthorpe
2024-05-24 23:15 ` Peter Xu
2024-05-24 13:42 ` Jason Gunthorpe
2024-05-30 0:09 ` Tian, Kevin
2024-05-30 2:22 ` Alex Williamson
2024-05-30 2:47 ` Tian, Kevin
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=20240524132433.GW20229@nvidia.com \
--to=jgg@nvidia.com \
--cc=ajones@ventanamicro.com \
--cc=alex.williamson@redhat.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=yan.y.zhao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.