On 11/7/19 10:24 AM, Miroslav Benes wrote:

quoted

In my test, I had a kernel tree, but only wanted to build the test modules.
Once I did a 'make modules SUBDIR=' or 'make M= ...' KBUILD_EXTMOD got flipped
on and the modules lost in-tree status.  No amount of googling could tell me
how to build a single in-tree directory of modules :(

"make lib/livepatch/test_klp_livepatch.ko" should do the trick. "make
lib/livepatch/" only builds the object files and I haven't found a way to
make it link .ko modules other than specifying them one by one directly.

Forgot to mention that this works too, but I was looking to script it 
and not have each .ko hardcoded in a series of make commands.  Anyway, 
it's a strange use-case and it was something I was only cooking up for 
an in-house continuous testing scenario.

quoted

And then it seemed that
opening the tests for OOT modules was reasonable anyway.

That's an interesting idea. If a module is in tree, it is under our
control. So we know what "testing capabilities" it offers. I guess that
with OOT testing modules the selftests would have to be smarter.

It would probably go hand in hand with custom test scripts that would 
understand the OOT module capabilities, I think.  I doubt anyone will 
try it (besides me), but the grep filter was there and it was an easy tweak.

-- Joe