On Tue, Mar 18, 2025 at 10:18 AM Joe Lawrence <[email protected]> wrote: [...] > >> Also, while poking at this today with virtme-ng, my initial attempt had > >> build a fairly minimal kernel without CONFIG_DYNAMIC_DEBUG. We can also > >> check for that via the sysfs interface to avoid confusing path-not-found > >> msgs, like the following ... > > > > We already have CONFIG_DYNAMIC_DEBUG=y in > > tools/testing/selftests/livepatch, so I think we don't need to check that > > again. > > > > Ah right. Do you know what script/file reads or sources that file? > (It's such a generic term that I get a bazillion grep hits.) When I run > `make -C tools/testing/selftests/livepatch run_tests` it just builds and > runs the tests regardless of the actual config.
I am not aware of any script reading the config file. It appears to be a convention that many subsystems follow. The subsystems may have some CI that reads these config files. Some subsystems use more complex logic around these config files. For example, bpf selftests have 6 config files and 4 DENYLIST. Thanks, Song
