All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim.Bird@sony.com <Tim.Bird@sony.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] lib: Add library function for parsing kernel config
Date: Thu, 15 Nov 2018 20:16:29 +0000	[thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF88A40F97@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <20181115134441.27359-1-chrubis@suse.cz>

> -----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:
KCONFIG_PATH
?

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



  parent reply	other threads:[~2018-11-15 20:16 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-15 13:44 [LTP] [PATCH] lib: Add library function for parsing kernel config Cyril Hrubis
2018-11-15 18:57 ` Cristian Marussi
2018-11-16 13:53   ` Cyril Hrubis
2018-11-15 20:16 ` Tim.Bird [this message]
2018-11-16 13:59   ` Cyril Hrubis
2018-11-21 19:53     ` Tim.Bird
2018-11-15 20:43 ` Tim.Bird
2018-11-16 13:57   ` Cyril Hrubis
2018-11-16  3:54 ` Pengfei Xu
2018-11-16  4:03   ` Tim.Bird
2018-11-16  4:57     ` Pengfei Xu
2018-11-16 14:00   ` Cyril Hrubis
2018-11-17  5:41     ` Pengfei Xu
2018-11-23  4:56 ` Sandeep Patil

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=ECADFF3FD767C149AD96A924E7EA6EAF88A40F97@USCULXMSG01.am.sony.com \
    --to=tim.bird@sony.com \
    --cc=ltp@lists.linux.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.