From: Shuah Khan <skhan@linuxfoundation.org>
To: "Bird, Tim" <Tim.Bird@sony.com>,
Marcos Paulo de Souza <mpdesouza@suse.de>,
"linux-kselftest@vger.kernel.org"
<linux-kselftest@vger.kernel.org>
Cc: "mbenes@suse.cz" <mbenes@suse.cz>,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: Purpose of gen_tar
Date: Wed, 25 Oct 2023 16:57:10 -0600 [thread overview]
Message-ID: <a3055ce6-8ca9-48ad-a299-8a0339374046@linuxfoundation.org> (raw)
In-Reply-To: <BYAPR13MB2503D83D75CC553E3D994AABFDDFA@BYAPR13MB2503.namprd13.prod.outlook.com>
On 10/24/23 12:34, Bird, Tim wrote:
>
>
>> -----Original Message----- From: Marcos Paulo de Souza
>> <mpdesouza@suse.de>
>>
> ...
>> Per the kselftests documentation[1], the gen_tar target is used to
>> package the tests to run "on different systems". But what if the
>> different system has different libraries/library versions? Wouldn't
>> it be a problem?
>>
> ...
>>
>> While the current approach can work when the selftests rely solely
>> on shell scripts(cpufreq, kexec), those who compile userspace
>> binaries (cgroup, alsa, sched, ...) may not work.
>>
>> Am I missing something? Is gen_tar only meant to copy the tests to
>> be run on systems with the same libraries or with the libraries
>> with the exactly the same version?
>
> gen_tar was originally intended (I believe) for developers doing
> cross-compilation. The SDK used for cross-compilation of the
> executables should handle issues such as library versions (and of
> course, CPU architecture and endian-ness).
>
> I've never done cross-compilation for the same architecture, so I
> don't know how that would work, but I presume there is some way to
> compile code for another system with the same architecture but
> different libraries.
Right. gen_tar was intended to be used when a user wants to generate tar
archive of all the complied tests/installed tests. Running kselftest_install
creates a directory with artifacts necessary to execute tests.
This functionality is now part of the selftests Makefile - gen_tar target will
do the same.
thanks,
-- Shuah
prev parent reply other threads:[~2023-10-25 22:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 18:21 Purpose of gen_tar Marcos Paulo de Souza
2023-10-24 18:34 ` Bird, Tim
2023-10-25 22:57 ` Shuah Khan [this message]
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=a3055ce6-8ca9-48ad-a299-8a0339374046@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=Tim.Bird@sony.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=mbenes@suse.cz \
--cc=mpdesouza@suse.de \
/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