[LTP] [PATCH] lib: Add library function for parsing kernel config

Tim.Bird@sony.com Tim.Bird@sony.com
Thu Nov 15 21:16:29 CET 2018

> -----Original Message-----
> From: Cyril Hrubis on Thursday, November 15, 2018 5:45 AM
> This is meant as last resort action for disabling tests if certain
> kernel funcitonality was not present, in general case runtime checks are
> prefered.
> For functionality that can be build as a module tst_check_driver() is
> most likely better fit since it will also insert requested kernel module
> into kernel if needed.
> For newly added syscalls kernel version comparsion and/or checking errno
> is prefered.
> However in rare cases certain core kernel functionality cannot be
> detected in any other way than checking the kernel config, which is
> where this API gets into the play.
> The path to the kernel config could be specified by LTP_KCONFIG
> environment variable, which also takes precedence before the
> autodetection that attempts to read the config from known locations.

It would be nice to use a variable name here that was not project-specific.

In Fuego, we automatically check a few different places, but we don't
check a location specified by an environment variable.  However, I've wanted to
add one.  I'd prefer to use the same one as other projects, if possible.

I'm shooting from the hip here, but how about something like:

Is this something that kernel-producing projects, such as Yocto Project
or Buildroot, (or Debian or Fedora, or the kernel Makefile, for that matter)
already have, or would be willing to support?

To others on the automated-testing list, does anyone else have a
variable used to specify the location of the kernel config file?  If so,
what's its name?

 -- Tim

More information about the ltp mailing list