From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
Luis Chamberlain <mcgrof@kernel.org>
Cc: Lucas De Marchi <lucas.de.marchi@gmail.com>,
"pmladek@suse.com" <pmladek@suse.com>,
"cl@linux.com" <cl@linux.com>, "mbenes@suse.cz" <mbenes@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"jeyu@kernel.org" <jeyu@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-modules@vger.kernel.org" <linux-modules@vger.kernel.org>,
"void@manifault.com" <void@manifault.com>,
"atomlin@atomlin.com" <atomlin@atomlin.com>,
"allen.lkml@gmail.com" <allen.lkml@gmail.com>,
"joe@perches.com" <joe@perches.com>,
"msuchanek@suse.de" <msuchanek@suse.de>,
"oleksandr@natalenko.name" <oleksandr@natalenko.name>,
"jason.wessel@windriver.com" <jason.wessel@windriver.com>,
"daniel.thompson@linaro.org" <daniel.thompson@linaro.org>,
Aaron Tomlin <atomlin@redhat.com>
Subject: Re: [PATCH v9 00/14] module: core code clean up
Date: Tue, 1 Mar 2022 17:43:44 +0000 [thread overview]
Message-ID: <20fddc03-4e31-d77a-024b-103d3c166d0f@csgroup.eu> (raw)
In-Reply-To: <20220301171555.tzrqrmhtv2tkxtaj@ldmartin-desk2>
Le 01/03/2022 à 18:15, Lucas De Marchi a écrit :
> On Tue, Mar 01, 2022 at 08:01:23AM -0800, Luis Chamberlain wrote:
>> On Tue, Mar 01, 2022 at 07:44:26AM +0000, Christophe Leroy wrote:
>>>
>>>
>>> Le 01/03/2022 à 01:21, Luis Chamberlain a écrit :
>>> >
>>> > We should run kmod tests as well.
>>> >
>>>
>>> I tried to build kmod tests, but I get a crazy result:
>>>
>>>
>>> $ ./configure --host=ppc-linux --prefix=/usr/local
>>>
>>> $ make
>>>
>>> $ cd testsuite
>>>
>>> $ make
>>>
>>> $ file test-list
>>> test-list: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1
>>> (SYSV), dynamically linked, interpreter /lib/ld.so.1, for GNU/Linux
>>> 3.2.0, with debug_info, not stripped
>>>
>>> $ file module-playground/mod-loop-a.ko
>>> module-playground/mod-loop-a.ko: ELF 64-bit LSB relocatable, x86-64,
>>> version 1 (SYSV),
>>> BuildID[sha1]=d46956a4fd36d8d3467806c31831c81217a573f5, with debug_info,
>>> not stripped
>>>
>>>
>>>
>>> How do I get it to crossbuild proper PowerPC module ?
>
> do I understand correctly that you want to crossbuild kmod + kernel
> modules to do your test? why?
Yes, I want to build the tests on my PC and run them on a powerpc board.
>
> If you really need it, then beware we just chainload the kernel build
> for the out-of-tree modules when compiling the test modules. Something
> like this should work:
>
> make V=1 KDIR=$HOME/p/gfx-internal/linux-arm64/ ARCH=arm64
> CROSS_COMPILE=aarch64-linux-gnu- check
>
> But running the cross built binaries is probably not what you want?
I want to run them on the board.
>
> Another thing is that unless you are patching kmod binaries or libkmod,
> the testsuite won't test much. kmod's testsuite don't test anything on
> the kernel side... the kernel part is mocked by the testsuite itself.
> Adding proper integration with the kernel part is possible, but not
> something ready.
Ah, I see.
I made non trivial modification on kernel modules handling (see series
at
https://patchwork.kernel.org/project/linux-modules/cover/cover.1645607143.git.christophe.leroy@csgroup.eu/)
and Luis suggested to run kmod test suite to perform regression testing.
Christophe
prev parent reply other threads:[~2022-03-01 17:43 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 23:43 [PATCH v9 00/14] module: core code clean up Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 01/14] module: Move all into module/ Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 02/14] module: Simple refactor in preparation for split Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 03/14] module: Make internal.h and decompress.c more compliant Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 04/14] module: Move livepatch support to a separate file Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 05/14] module: Move latched RB-tree " Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 06/14] module: Move strict rwx " Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 07/14] module: Move extra signature support out of core code Aaron Tomlin
2022-03-02 8:08 ` Christophe Leroy
2022-03-02 13:33 ` Aaron Tomlin
2022-03-02 13:41 ` Christophe Leroy
2022-03-05 20:37 ` Aaron Tomlin
2022-03-06 17:46 ` Christophe Leroy
2022-03-07 9:38 ` Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 08/14] module: Move kmemleak support to a separate file Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 09/14] module: Move kallsyms support into " Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 10/14] module: kallsyms: Fix suspicious rcu usage Aaron Tomlin
2022-03-01 16:52 ` Aaron Tomlin
2022-03-02 17:02 ` Aaron Tomlin
2022-03-02 22:24 ` Luis Chamberlain
2022-02-28 23:43 ` [PATCH v9 11/14] module: Move procfs support into a separate file Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 12/14] module: Move sysfs " Aaron Tomlin
2022-02-28 23:43 ` [PATCH v9 13/14] module: Move kdb_modules list out of core code Aaron Tomlin
2022-03-02 16:19 ` Daniel Thompson
2022-03-02 16:26 ` Daniel Thompson
2022-03-02 20:31 ` Aaron Tomlin
2022-03-02 20:56 ` Christophe Leroy
2022-03-02 22:46 ` Luis Chamberlain
2022-03-03 10:44 ` Aaron Tomlin
2022-03-03 14:57 ` Luis Chamberlain
2022-03-03 13:37 ` Christoph Hellwig
2022-03-03 14:59 ` Daniel Thompson
2022-03-03 17:54 ` Christoph Hellwig
2022-03-03 18:16 ` Christophe Leroy
2022-03-03 19:00 ` Christoph Hellwig
2022-03-03 19:21 ` Luis Chamberlain
2022-03-04 11:12 ` Aaron Tomlin
2022-03-04 11:54 ` Daniel Thompson
2022-03-04 11:59 ` Aaron Tomlin
2022-03-03 12:55 ` Daniel Thompson
2022-02-28 23:43 ` [PATCH v9 14/14] module: Move version support into a separate file Aaron Tomlin
2022-03-01 0:21 ` [PATCH v9 00/14] module: core code clean up Luis Chamberlain
2022-03-01 7:07 ` Christophe Leroy
2022-03-01 16:00 ` Luis Chamberlain
2022-03-01 7:44 ` Christophe Leroy
2022-03-01 16:01 ` Luis Chamberlain
2022-03-01 17:15 ` Lucas De Marchi
2022-03-01 17:43 ` Christophe Leroy [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=20fddc03-4e31-d77a-024b-103d3c166d0f@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=atomlin@atomlin.com \
--cc=atomlin@redhat.com \
--cc=cl@linux.com \
--cc=daniel.thompson@linaro.org \
--cc=jason.wessel@windriver.com \
--cc=jeyu@kernel.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lucas.de.marchi@gmail.com \
--cc=lucas.demarchi@intel.com \
--cc=mbenes@suse.cz \
--cc=mcgrof@kernel.org \
--cc=msuchanek@suse.de \
--cc=oleksandr@natalenko.name \
--cc=pmladek@suse.com \
--cc=void@manifault.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;
as well as URLs for NNTP newsgroup(s).