[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZfnXDfjyHPz9JDSo@memverge.com>
Date: Tue, 19 Mar 2024 14:18:53 -0400
From: Gregory Price <gregory.price@...verge.com>
To: Matthew Wilcox <willy@...radead.org>
Cc: Gregory Price <gourry.memverge@...il.com>, linux-mm@...ck.org,
linux-api@...r.kernel.org, linux-arch@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org,
ying.huang@...el.com, dan.j.williams@...el.com, honggyu.kim@...com,
corbet@....net, arnd@...db.de, luto@...nel.org,
akpm@...ux-foundation.org, shuah@...nel.org
Subject: Re: [RFC v3 3/3] ktest: sys_move_phys_pages ktesty
On Tue, Mar 19, 2024 at 02:16:01PM -0400, Gregory Price wrote:
> On Tue, Mar 19, 2024 at 06:08:39PM +0000, Matthew Wilcox wrote:
> > On Tue, Mar 19, 2024 at 05:52:46PM +0000, Matthew Wilcox wrote:
> > > On Tue, Mar 19, 2024 at 01:26:09PM -0400, Gregory Price wrote:
> > > > Implement simple ktest that looks up the physical address via
> > > > /proc/self/pagemap and migrates the page based on that information.
> > >
> > > What? LOL. No.
> >
> > Also, how is this v3 and the first one to land on linux-mm?
> >
> > https://lore.kernel.org/linux-mm/?q=move_phys_pages
> >
> > Also, where is the syscall itself? The only thing here is the ktest.
> >
>
> OH, I see the confusion now.
>
> There were two other versions, and I have experienced this delivery
> failure before, i'm not sure why the other commits have not been delivered.
>
> Let me look into this.
>
> ~Gregory
>
Full set of patches:
https://lore.kernel.org/all/20240319172609.332900-1-gregory.price@memverge.com/
I've experienced silent linux-mm delivery failures like this before, I
still do not understand this issue.
v1:
https://lore.kernel.org/all/20230907075453.350554-1-gregory.price@memverge.com/
v2:
https://lore.kernel.org/all/20230919230909.530174-1-gregory.price@memverge.com/
~Gregory
Powered by blists - more mailing lists