From: Jason Gunthorpe <jgg@nvidia.com>
To: Steven Sistare <steven.sistare@oracle.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [RFC V1 0/4] iommufd live update
Date: Thu, 22 Aug 2024 18:10:39 -0300 [thread overview]
Message-ID: <20240822211039.GY3773488@nvidia.com> (raw)
In-Reply-To: <1fd5610b-998b-438a-8959-2dc7f3ed8afa@oracle.com>
On Thu, Aug 22, 2024 at 05:05:19PM -0400, Steven Sistare wrote:
> When iommufd supports mapping them (I assume someone is working on that?),
> mdev access to those mappings must work after live update. We must be
> able to translate iova to PFN without using va, by recognizing the mapping
> is special and calling something special to generate the PFN, such as
> the extracted guts of vfio_pci_mmap_fault.
I intend to support MMIO via dmabuf, the current VMA approach cannot
ever be correctly locked.
So it will work the same as this in that vision, there are patches in
progress for the parts, it is unexpectedly big :(
Jason
next prev parent reply other threads:[~2024-08-22 21:10 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-20 18:56 [RFC V1 0/4] iommufd live update Steve Sistare
2024-07-20 18:56 ` [RFC V1 1/4] iommufd: Export do_update_pinned Steve Sistare
2024-07-20 18:56 ` [RFC V1] iommufd debug print Steve Sistare
2024-07-20 19:01 ` Steven Sistare
2024-07-20 18:56 ` [RFC V1 2/4] iommufd: Lock all objects Steve Sistare
2024-07-22 15:37 ` Jason Gunthorpe
2024-08-05 19:01 ` Steven Sistare
2024-09-26 14:00 ` Steven Sistare
2024-07-20 18:56 ` [RFC V1 3/4] iommufd: Add IOMMU_IOAS_CHANGE_PROCESS Steve Sistare
2024-07-20 18:56 ` [RFC V1 4/4] iommufd: update VA Steve Sistare
2024-07-22 15:51 ` Jason Gunthorpe
2024-08-05 19:02 ` Steven Sistare
2024-08-06 12:54 ` Jason Gunthorpe
2024-07-20 19:21 ` [RFC V1 0/4] iommufd live update Steven Sistare
2024-07-22 15:55 ` Jason Gunthorpe
2024-08-05 19:03 ` Steven Sistare
2024-08-06 12:56 ` Jason Gunthorpe
2024-08-08 19:15 ` Steven Sistare
2024-08-08 19:52 ` Jason Gunthorpe
2024-08-12 17:41 ` Steven Sistare
2024-08-19 14:59 ` Jason Gunthorpe
2024-08-21 17:54 ` Steven Sistare
2024-08-21 18:04 ` Jason Gunthorpe
2024-08-22 21:05 ` Steven Sistare
2024-08-22 21:10 ` Jason Gunthorpe [this message]
2024-07-23 12:48 ` Jason Gunthorpe
2024-08-05 19:02 ` Steven Sistare
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=20240822211039.GY3773488@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=kevin.tian@intel.com \
--cc=steven.sistare@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox