From: Alex Mastro <amastro@fb.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alex Mastro <amastro@fb.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Kevin Tian <kevin.tian@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>,
David Reiss <dreiss@meta.com>, Joerg Roedel <joro@8bytes.org>,
Keith Busch <kbusch@kernel.org>,
Leon Romanovsky <leon@kernel.org>,
Li Zhe <lizhe.67@bytedance.com>,
Mahmoud Adam <mngyadam@amazon.de>,
Philipp Stanner <pstanner@redhat.com>,
Robin Murphy <robin.murphy@arm.com>,
Vivek Kasireddy <vivek.kasireddy@intel.com>,
Will Deacon <will@kernel.org>, Yunxiang Li <Yunxiang.Li@amd.com>,
<linux-kernel@vger.kernel.org>, <iommu@lists.linux.dev>,
<kvm@vger.kernel.org>
Subject: Re: [TECH TOPIC] vfio, iommufd: Enabling user space drivers to vend more granular access to client processes
Date: Fri, 19 Sep 2025 10:14:58 -0700 [thread overview]
Message-ID: <20250919171459.1352524-1-amastro@fb.com> (raw)
In-Reply-To: <20250919095743.482a00cd.alex.williamson@redhat.com>
On Fri, Sep 19, 2025 at 09:57:43AM -0600, Alex Williamson wrote:
> Definitely. Also, is this at all considering the work that's gone into
> vfio-user? The long running USD sounds a lot like a vfio-user server,
> where if we're using vfio-user's socket interface we'd have a lot of
> opportunity to implement policy there and dma-bufs might be a means to
> expose direct, restricted access. Thanks,
Possibly. Though I think the USD's responsibilities and the semantics for
how clients would negotiate various forms of device access would be very
application-dependent. In addition to just vending vfio and iommu-related fds,
our USD needs to do things like bootstrap the device by loading firmwares,
collect metrics, and other background functionality.
I'm not sure if I'm addressing your point though.
We actually do use libvfio-user [1] for user space simulation of PCI devices,
but it's not a part of our USD today.
[1] https://github.com/nutanix/libvfio-user
Alex
next prev parent reply other threads:[~2025-09-19 17:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 21:44 Alex Mastro
2025-09-18 22:57 ` Jason Gunthorpe
2025-09-18 23:24 ` Keith Busch
2025-09-19 7:00 ` Tian, Kevin
2025-09-19 11:58 ` Jason Gunthorpe
2025-09-22 9:14 ` Mostafa Saleh
2025-09-22 17:46 ` Alex Mastro
2025-09-22 17:51 ` Jason Gunthorpe
2025-09-19 11:56 ` Jason Gunthorpe
2025-09-19 15:57 ` Alex Williamson
2025-09-19 17:14 ` Alex Mastro [this message]
2025-09-19 16:13 ` Alex Mastro
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=20250919171459.1352524-1-amastro@fb.com \
--to=amastro@fb.com \
--cc=Yunxiang.Li@amd.com \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=dreiss@meta.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kbusch@kernel.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhe.67@bytedance.com \
--cc=mngyadam@amazon.de \
--cc=pstanner@redhat.com \
--cc=robin.murphy@arm.com \
--cc=vivek.kasireddy@intel.com \
--cc=will@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®