From: Matthew Wilcox <willy@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Sidhartha Kumar <sidhartha.kumar@oracle.com>,
akpm@linux-foundation.org, christophe.leroy@csgroup.eu,
justinstitt@google.com, linux-kernel@vger.kernel.org,
linux-m68k@lists.linux-m68k.org, linuxppc-dev@lists.ozlabs.org,
llvm@lists.linux.dev, maddy@linux.ibm.com, morbo@google.com,
mpe@ellerman.id.au, nathan@kernel.org, naveen@kernel.org,
ndesaulniers@google.com, npiggin@gmail.com, linux-mm@kvack.org
Subject: Re: [PATCH] xarray: port tests to kunit
Date: Thu, 30 Jan 2025 14:22:40 +0000 [thread overview]
Message-ID: <Z5uLMC7J4KKjuax4@casper.infradead.org> (raw)
In-Reply-To: <CAMuHMdVcuhzO57Qn-kcUJDM=HmkSwuheyNJPF1tx+gxRKnKZXA@mail.gmail.com>
On Thu, Jan 30, 2025 at 09:21:12AM +0100, Geert Uytterhoeven wrote:
> The long and obscure command line is a red herring: a simple
> "modprobe test_xarray" is all it takes...
That's all I've ever done. I'm confused/annoyed by all this "let's
wrap everything up in some complex and obscure new thing" practice.
> > You should look at the userspace testing (that this broke) as it has
> > been really useful in certain scenarios.
>
> BTW, how do I even build tools/testing/radix-tree?
> "make tools/help" doesn't show the radix-tree test.
> "make tools/all" doesn't seem to try to build it.
> Same for "make kselftest-all".
I've never heard of any of those things. So I didn't try to make any of
them work.
> When trying the above, and ignoring failures due to missing packages
> on my host:
> - there are several weird build errors,
> - this doesn't play well with O=,
> - lots of scary warnings when building for 32-bit,
> - ...
Really? Turns out I haven't built for 32-bit on this laptop, so I'm
installing all the packages I need now. I seem to reemember it being
painful due to liburcu packaging not allowing me to install both a
32-bit and 64-bit package at the same time.
> At least the kunit tests build (and run[1] ;-) most of the time...
That's unworthy. kunit isn't trying to do anything nearly as hard
as the radix tree tests are.
> [1] test_xarray started failing on m68k recently
> https://lore.kernel.org/all/CAMuHMdU_bfadUO=0OZ=AoQ9EAmQPA4wsLCBqohXR+QCeCKRn4A@mail.gmail.com/
I really wish Andrew would stop merging xarray patches.
next prev parent reply other threads:[~2025-01-30 14:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 15:11 [PATCH] xarray: port tests to kunit Tamir Duberstein
2025-01-29 21:02 ` Sidhartha Kumar
2025-01-29 21:26 ` Liam R. Howlett
2025-01-29 21:28 ` Tamir Duberstein
2025-01-29 22:26 ` Liam R. Howlett
2025-01-29 22:33 ` Tamir Duberstein
2025-01-29 23:02 ` Matthew Wilcox
2025-01-29 23:08 ` Tamir Duberstein
2025-01-29 23:11 ` Matthew Wilcox
2025-01-29 23:17 ` Tamir Duberstein
2025-01-30 8:21 ` Geert Uytterhoeven
2025-01-30 12:51 ` Liam R. Howlett
2025-01-30 13:25 ` Geert Uytterhoeven
2025-01-30 14:05 ` Liam R. Howlett
2025-01-30 14:24 ` Geert Uytterhoeven
2025-01-30 15:16 ` Liam R. Howlett
2025-01-31 7:39 ` Geert Uytterhoeven
2025-01-30 14:09 ` Lorenzo Stoakes
2025-01-30 14:38 ` Geert Uytterhoeven
2025-01-30 14:49 ` Lorenzo Stoakes
2025-01-30 14:22 ` Matthew Wilcox [this message]
2025-01-31 0:22 ` Andrew Morton
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=Z5uLMC7J4KKjuax4@casper.infradead.org \
--to=willy@infradead.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@csgroup.eu \
--cc=geert@linux-m68k.org \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=llvm@lists.linux.dev \
--cc=maddy@linux.ibm.com \
--cc=morbo@google.com \
--cc=mpe@ellerman.id.au \
--cc=nathan@kernel.org \
--cc=naveen@kernel.org \
--cc=ndesaulniers@google.com \
--cc=npiggin@gmail.com \
--cc=sidhartha.kumar@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