From: Kevin Brodsky <kevin.brodsky@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Ryan Roberts <ryan.roberts@arm.com>,
Shuah Khan <shuah@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Yunsheng Lin <linyunsheng@huawei.com>
Subject: Re: [PATCH 1/4] selftests/mm: remove flaky header check
Date: Mon, 5 Jan 2026 19:13:16 +0100 [thread overview]
Message-ID: <4ad1bc4e-b1dc-46a3-845b-e648e4304ad4@arm.com> (raw)
In-Reply-To: <2bc4e09a-045a-4d33-8857-1bdfe3281da2@sirena.org.uk>
On 05/01/2026 13:46, Mark Brown wrote:
> On Mon, Dec 29, 2025 at 04:40:26PM +0100, Kevin Brodsky wrote:
>> On 18/12/2025 15:25, Mark Brown wrote:
>>> Well, there's also the selection of KDIR which for some reason defaults
>>> to the installed kernel so we get:
>> Overall the kselftests tend to assume that we're building on the same
>> machine we'll run them, so at least that feels consistent. The same
>> default is used for most other out-of-tree kselftests modules
>> (livepatch, net/bench).
> That's really not the expected usage pattern, I'd be surprised if a
> non-trivial propoprtion of kselftest builds were intended to be run on
> the system they're built on - a lot of people test interactively in VMs,
> or on some other target hardware, and automated systems are going to be
> building separately. The two you've identified look like special
> snowflakes TBH (livepatch in particular has a bunch of other issues due
> to what it's trying to do).
>
>> Maybe the documentation should be updated to recommend setting KDIR
>> explicitly? Or maybe it could default to KDIR=$PWD or $(abspath
>> $(KBUILD_OUTPUT)) when cross-compiling?
> I think defaulting to something related to the current kernel build is
> more sensible here.
Fair enough, fine by me. Then I'll change the default to the output
directory and remove the header check.
- Kevin
next prev parent reply other threads:[~2026-01-05 18:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 14:26 [PATCH 0/4] Various mm kselftests improvements/fixes Kevin Brodsky
2025-12-16 14:26 ` [PATCH 1/4] selftests/mm: remove flaky header check Kevin Brodsky
2025-12-17 3:18 ` Yunsheng Lin
2025-12-17 9:58 ` Kevin Brodsky
2025-12-18 7:21 ` Yunsheng Lin
2025-12-17 10:04 ` Mark Brown
2025-12-18 13:24 ` Kevin Brodsky
2025-12-18 14:25 ` Mark Brown
2025-12-29 15:40 ` Kevin Brodsky
2026-01-05 12:46 ` Mark Brown
2026-01-05 18:13 ` Kevin Brodsky [this message]
2025-12-16 14:26 ` [PATCH 2/4] selftests/mm: pass down full CC and CFLAGS to check_config.sh Kevin Brodsky
2025-12-18 8:04 ` David Hildenbrand (Red Hat)
2025-12-16 14:26 ` [PATCH 3/4] selftests/mm: fix faulting-in code in pagemap_ioctl test Kevin Brodsky
2025-12-16 14:56 ` Ryan Roberts
2025-12-16 15:11 ` Kevin Brodsky
2025-12-18 8:05 ` David Hildenbrand (Red Hat)
2025-12-18 13:18 ` Kevin Brodsky
2025-12-19 8:29 ` David Hildenbrand (Red Hat)
2025-12-29 11:46 ` Kevin Brodsky
2025-12-16 14:26 ` [PATCH 4/4] selftests/mm: fix exit code in pagemap_ioctl Kevin Brodsky
2025-12-16 14:58 ` Ryan Roberts
2025-12-17 10:08 ` Mark Brown
2025-12-18 13:20 ` Kevin Brodsky
2025-12-18 8:07 ` David Hildenbrand (Red Hat)
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=4ad1bc4e-b1dc-46a3-845b-e648e4304ad4@arm.com \
--to=kevin.brodsky@arm.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linyunsheng@huawei.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=pabeni@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
/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