From: Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: shuah <shuah@kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kselftest@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: kselftest OOT run_tests
Date: Wed, 27 May 2020 10:34:51 +0300 [thread overview]
Message-ID: <xunypnapomp0.fsf@redhat.com> (raw)
In-Reply-To: <fcd9debe-4bed-df1a-d5ea-69e0a8d0ac98@redhat.com> (Joe Lawrence's message of "Tue, 26 May 2020 16:40:06 -0400")
Hi, Joe!
>>>>> On Tue, 26 May 2020 16:40:06 -0400, Joe Lawrence wrote:
> On 5/26/20 1:13 PM, shuah wrote:
>> On 5/25/20 7:55 AM, Yauheni Kaliuta wrote:
>>> Hi!
>>>
>>> I'm wondering how out of tree check is supposed to work for make
>>> O=dir run_tests from selftests (or make -C ...) directory?
>>>
>>> (both with 051f278e9d81 ("kbuild: replace KBUILD_SRCTREE with
>>> boolean building_out_of_srctree") and without)
>>>
>>> make M= ... does not work with run_tests.
>>>
>>
>> Kselftests run_tests target isn't intended for building and running
>> tests OOT. Also make M= doesn't make sense for them.
>>
>> There is no support to build OOT at the moment. I would like to get
>> a better understanding of your use-case. Can you elaborate?
>>
> Hey Yauheni, can you CC me on the use-case explanation?
> We currently do something really silly for the livepatch
> selftests on RHEL-7 for CKI that requires building them as
> pseudo OOT... in our case, we'd like to just be able to do
> something like make modules_prepare && make M= lib/livepatch,
> so perhaps a bit different... but I'd be curious for which
> problem you're currently trying to solve.
I care about `make install` for tests at the moment, for CI. For
CI you need to build kernel, install (and save/pack) the tests,
then boot the kernel and run the tests. It deals with OUTPUT, I
looked how to do it properly and found what I found.
My understanding, that it was supposed to work the way you
described. But looks like I'm wrong.
--
WBR,
Yauheni Kaliuta
next prev parent reply other threads:[~2020-05-27 7:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 13:55 kselftest OOT run_tests Yauheni Kaliuta
2020-05-26 17:13 ` shuah
2020-05-26 20:40 ` Joe Lawrence
2020-05-27 7:34 ` Yauheni Kaliuta [this message]
2020-05-27 7:30 ` Yauheni Kaliuta
2020-05-27 18:22 ` shuah
2020-05-27 18:40 ` Yauheni Kaliuta
2020-05-27 21:46 ` shuah
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=xunypnapomp0.fsf@redhat.com \
--to=yauheni.kaliuta@redhat.com \
--cc=bpf@vger.kernel.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
--cc=yamada.masahiro@socionext.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