From: Steven Sistare <steven.sistare@oracle.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: iommu@lists.linux.dev, Kevin Tian <kevin.tian@intel.com>,
Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Subject: Re: [PATCH V3 4/4] iommufd: IOMMU_IOAS_CHANGE_PROCESS selftest
Date: Thu, 7 Nov 2024 15:47:35 -0500 [thread overview]
Message-ID: <0bfbdfb9-eab1-4e16-a19c-eb6c73b4c3c9@oracle.com> (raw)
In-Reply-To: <20241107202607.GG539304@nvidia.com>
On 11/7/2024 3:26 PM, Jason Gunthorpe wrote:
> On Mon, Oct 07, 2024 at 10:13:23AM -0700, Steve Sistare wrote:
>> Add selftest cases for IOMMU_IOAS_CHANGE_PROCESS.
>>
>> Signed-off-by: Steve Sistare <steven.sistare@oracle.com>
>> ---
>> tools/testing/selftests/iommu/Makefile | 1 +
>> tools/testing/selftests/iommu/iommufd.c | 148 ++++++++++++++++++++++++--
>> tools/testing/selftests/iommu/iommufd_utils.h | 34 +++---
>> 3 files changed, 163 insertions(+), 20 deletions(-)
>
> Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
Cool, thanks!
I'll post V4 with minor changes to the self test code.
- Steve
prev parent reply other threads:[~2024-11-07 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 17:13 [PATCH V3 0/4] iommufd live update Steve Sistare
2024-10-07 17:13 ` [PATCH V3 1/4] iommufd: Export do_update_pinned Steve Sistare
2024-10-07 17:13 ` [PATCH V3 2/4] iommufd: Lock all objects Steve Sistare
2024-11-07 20:23 ` Jason Gunthorpe
2024-10-07 17:13 ` [PATCH V3 3/4] iommufd: Add IOMMU_IOAS_CHANGE_PROCESS Steve Sistare
2024-11-06 18:08 ` Jason Gunthorpe
2024-11-06 18:55 ` Steven Sistare
2024-11-07 20:25 ` Jason Gunthorpe
2024-10-07 17:13 ` [PATCH V3 4/4] iommufd: IOMMU_IOAS_CHANGE_PROCESS selftest Steve Sistare
2024-11-07 20:26 ` Jason Gunthorpe
2024-11-07 20:47 ` Steven Sistare [this message]
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=0bfbdfb9-eab1-4e16-a19c-eb6c73b4c3c9@oracle.com \
--to=steven.sistare@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=kevin.tian@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox