Linux IOMMU Development
 help / color / mirror / Atom feed
From: Steven Sistare <steven.sistare@oracle.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
	Nicolin Chen <nicolinc@nvidia.com>
Subject: Re: [PATCH V7 0/9] iommu_ioas_map_file
Date: Mon, 4 Nov 2024 08:58:29 -0500	[thread overview]
Message-ID: <b4fa2db8-192f-4cfd-880a-5e29bad58f52@oracle.com> (raw)
In-Reply-To: <1bde901c-980a-44e0-8f6f-8e1985683349@oracle.com>

On 10/30/2024 8:43 AM, Steven Sistare wrote:
> On 10/29/2024 8:11 PM, Jason Gunthorpe wrote:
>> On Fri, Oct 25, 2024 at 06:11:50AM -0700, Steve Sistare wrote:
>>> Provide the IOMMU_IOAS_MAP_FILE ioctl, which allows a user to register
>>> memory by passing a memfd plus offset and length.  Implement it using
>>> the memfd_map_folios KAPI, and the proposed folio_add_pins KAPI.
>>> See the individual patches for details.
>>>
>>> Steve Sistare (9):
>>>    mm/gup: folio_add_pins
>>>    iommufd: rename uptr in iopt_alloc_iova
>>>    iommufd: generalize iopt_pages address
>>>    iommufd: pfn reader local variables
>>>    iommufd: folio subroutines
>>>    iommufd: pfn reader for file mappings
>>>    iommufd: IOMMU_IOAS_MAP_FILE
>>>    iommufd: file mappings for mdev
>>>    iommufd: map file selftest
>>
>> Applied to iommufd for-next
>>
>> Is v3 still the latest for "iommufd live update"?
> 
> Yes.
> 
> It's selftest patch no longer applies cleanly, but I'll fix that in V4
> after you review the other patches.  Thanks!

Just checking -- are you waiting for me to post V4 before reviewing any
further?

- Steve


  reply	other threads:[~2024-11-04 13:59 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 13:11 [PATCH V7 0/9] iommu_ioas_map_file Steve Sistare
2024-10-25 13:11 ` [PATCH V7 1/9] mm/gup: folio_add_pins Steve Sistare
2024-10-25 13:11 ` [PATCH V7 2/9] iommufd: rename uptr in iopt_alloc_iova Steve Sistare
2024-10-25 13:11 ` [PATCH V7 3/9] iommufd: generalize iopt_pages address Steve Sistare
2024-10-25 13:11 ` [PATCH V7 4/9] iommufd: pfn reader local variables Steve Sistare
2024-10-25 13:11 ` [PATCH V7 5/9] iommufd: folio subroutines Steve Sistare
2024-10-25 13:11 ` [PATCH V7 6/9] iommufd: pfn reader for file mappings Steve Sistare
2024-10-31  3:34   ` Alexey Kardashevskiy
2024-11-06  3:18     ` Alexey Kardashevskiy
2024-11-06 13:19       ` Steven Sistare
2024-11-07 10:00         ` Alexey Kardashevskiy
2024-11-07 13:21           ` Steven Sistare
2024-11-07 14:08           ` Jason Gunthorpe
2024-11-08  0:01             ` Alexey Kardashevskiy
2024-11-14  4:03               ` Alexey Kardashevskiy
2024-11-14 16:17                 ` Jason Gunthorpe
2024-11-18  1:24                   ` Alexey Kardashevskiy
2024-10-25 13:11 ` [PATCH V7 7/9] iommufd: IOMMU_IOAS_MAP_FILE Steve Sistare
2024-10-25 13:11 ` [PATCH V7 8/9] iommufd: file mappings for mdev Steve Sistare
2024-10-25 13:11 ` [PATCH V7 9/9] iommufd: map file selftest Steve Sistare
2024-10-25 13:14   ` Steven Sistare
2024-10-25 17:00     ` Nicolin Chen
2024-10-25 17:04   ` Nicolin Chen
2024-10-25 17:58     ` Steven Sistare
2024-10-25 18:39       ` Nicolin Chen
2024-10-25 23:58         ` Jason Gunthorpe
2024-10-26 19:13           ` Steven Sistare
2024-10-26 19:16             ` Steven Sistare
2024-10-26 23:09               ` Nicolin Chen
2024-10-27 14:38                 ` Steven Sistare
2024-10-30  0:11 ` [PATCH V7 0/9] iommu_ioas_map_file Jason Gunthorpe
2024-10-30 12:43   ` Steven Sistare
2024-11-04 13:58     ` Steven Sistare [this message]
2024-11-04 14:18       ` Jason Gunthorpe
2024-11-04 14:24         ` 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=b4fa2db8-192f-4cfd-880a-5e29bad58f52@oracle.com \
    --to=steven.sistare@oracle.com \
    --cc=iommu@lists.linux.dev \
    --cc=jgg@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=nicolinc@nvidia.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