From: Nicolin Chen <nicolinc@nvidia.com>
To: Steven Sistare <steven.sistare@oracle.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>, <iommu@lists.linux.dev>,
Kevin Tian <kevin.tian@intel.com>
Subject: Re: [PATCH V7 9/9] iommufd: map file selftest
Date: Sat, 26 Oct 2024 16:09:36 -0700 [thread overview]
Message-ID: <Zx12sBalOPZBlZOm@Asurada-Nvidia> (raw)
In-Reply-To: <1af8d6b6-6640-4299-b279-eaf943707664@oracle.com>
On Sat, Oct 26, 2024 at 03:16:36PM -0400, Steven Sistare wrote:
> On 10/26/2024 3:13 PM, Steven Sistare wrote:
> > On 10/25/2024 7:58 PM, Jason Gunthorpe wrote:
> > > On Fri, Oct 25, 2024 at 11:39:40AM -0700, Nicolin Chen wrote:
> > >
> > > > > I will try to reproduce your failures.
> > > > > What is your base commit?
> > > >
> > > > I was using the for-next tree (rc1) from:
> > > > git git://git.kernel.org/pub/scm/linux/kernel/git/jgg/iommufd.git
> > > >
> > > > And it was failing, so I guess rc1 is missing something for memfd.
> > > > So, it should be a false alarm.
> > >
> > > Oh, that's exciting. So I will have to base it on a rc that works so
> > > bisection works :\
> >
> > I'll test builds on arm to identify the minimum requirement.
>
> BTW this is likely an arm-specific issue, because I have been using
> for-next rc1 on x86, and all tests pass.
I did a clean build today. And it passes with for-next tree.
Looks like something wrong with my yesterday's build. Sorry.
Nicolin
next prev parent reply other threads:[~2024-10-26 23:09 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 [this message]
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
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=Zx12sBalOPZBlZOm@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--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