[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALzav=djghffsrexibhTK5AGsNe=QmHNfm-64NSP0OAGE+K6MQ@mail.gmail.com>
Date: Mon, 10 Nov 2025 15:10:29 -0800
From: David Matlack <dmatlack@...gle.com>
To: Alex Williamson <alex@...zbot.org>
Cc: Alex Mastro <amastro@...com>, Alex Williamson <alex.williamson@...hat.com>,
Jason Gunthorpe <jgg@...pe.ca>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] vfio: selftests: Skip vfio_dma_map_limit_test if mapping
returns -EINVAL
On Mon, Nov 10, 2025 at 11:45 AM David Matlack <dmatlack@...gle.com> wrote:
>
> On Mon, Nov 10, 2025 at 10:38 AM Alex Williamson <alex@...zbot.org> wrote:
> >
> > On Mon, 10 Nov 2025 18:00:08 +0000
> > David Matlack <dmatlack@...gle.com> wrote:
> > > AlexW, how much time do we have to get AlexM's series ready? I am fine
> > > with doing (3), then (2), and dropping (1) if there's enough time.
> >
> > I'll certainly agree that it'd be a much better precedent if the self
> > test were initially working, but also we should not increase the scope
> > beyond what we need to make it work for v6.18. If we can get that done
> > in the next day or two, add it to linux-next mid-week, and get Linus to
> > pull for rc6, I think that'd be reasonable. Thanks,
>
> Ack. I'll send a small series with this patch plus a patch to replace
> iova=vaddr with iova=4G, and we can use that as a back-up plan if
> AlexM's iova allocator isn't ready in time for 6.18.
I think we have a good chance to get the allocator series ready in
time for 6.18 (AlexM is quick :), so I'll hold off on sending a v2 of
my short term fixes.
Powered by blists - more mailing lists