From: Petr Mladek <pmladek@suse.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: Shuah Khan <skhan@linuxfoundation.org>,
Marcos Paulo de Souza <mpdesouza@suse.com>,
live-patching@vger.kernel.org, linux-kselftest@vger.kernel.org,
shuah@kernel.org, jpoimboe@redhat.com, mbenes@suse.cz
Subject: Re: [PATCH 0/2] livepatch: Move tests from lib/livepatch to selftests/livepatch
Date: Fri, 10 Jun 2022 16:48:32 +0200 [thread overview]
Message-ID: <YqNZwBWJmi5E/Nvo@alley> (raw)
In-Reply-To: <5966397b-5577-8075-ffdd-f32e5e4ca75a@redhat.com>
On Fri 2022-06-10 09:06:16, Joe Lawrence wrote:
> On 6/9/22 4:16 PM, Shuah Khan wrote:
> > On 6/3/22 8:32 AM, Marcos Paulo de Souza wrote:
> >> Hi there,
> >>
> >> The first patch moves the current livepatch tests to selftests,
> >> allowing it
> >> be better suited to contain more complex tests, like using userspace C
> >> code
> >> to use the livepatched kernel code. As a bonus it allows to use
> >> "gen_tar" to export the livepatch selftests, rebuild the modules by
> >> running make in selftests/livepatch directory and simplifies the process
> >> of creating and debugging new selftests.
> >>
> >
> > In general selftests don't include modules. We keep test modules under lib.
> > One of the reasons is that modules have dependencies on the kernel and
> > should
> > be built when kernel is built.
> >
> > I don't fully buy the argument that moving modules under selftest would
> > simplify
> > the process.
> >
>
> Hi Shuah,
>
> I see that there is tools/testing/selftests/bpf/bpf_testmod/ which
> claims to be a "conceptually out-of-tree module". Would similarly
> moving livepatch test modules under tools/ give us flexibility to write
> them build for multiple kernel versions? Then one could theoretically
> build and run the latest, greatest selftests against older kernels
> (assuming the associate script/module/kernel supports the idea)?
+1
Another motivation is that the new selftest also needs
an executable binary. It would be nice to handle both modules
and binaries the same way.
Honestly, lib/* is a mess. It mixes real functionality and test
modules. The relation between the modules and tools/testing/*
is far from clear. IMHO, it would be more clean to have the related
stuff together.
Of course, we could not move all test modules from lib/* easily.
Some of them might be used on its own or even as built-in
tests. But preventing the move looks like a step in
the wrong direction to me.
Best Regards,
Petr
next prev parent reply other threads:[~2022-06-10 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 14:32 [PATCH 0/2] livepatch: Move tests from lib/livepatch to selftests/livepatch Marcos Paulo de Souza
2022-06-03 14:32 ` [PATCH 1/2] " Marcos Paulo de Souza
2022-06-09 20:00 ` Shuah Khan
2022-06-09 20:13 ` Shuah Khan
2022-06-03 14:32 ` [PATCH 2/2] selftests: livepatch: Test livepatching a heavily called syscall Marcos Paulo de Souza
2022-06-17 21:17 ` Joe Lawrence
2022-06-09 20:16 ` [PATCH 0/2] livepatch: Move tests from lib/livepatch to selftests/livepatch Shuah Khan
2022-06-10 13:06 ` Joe Lawrence
2022-06-10 14:48 ` Petr Mladek [this message]
2022-06-14 1:02 ` Shuah Khan
2022-06-10 13:50 ` Marcos Paulo de Souza
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=YqNZwBWJmi5E/Nvo@alley \
--to=pmladek@suse.com \
--cc=joe.lawrence@redhat.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=live-patching@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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