public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: CONFIG_* used by user-space to figure out whether a feature is on/off
Date: Mon, 15 Jul 2013 11:40:50 -0400	[thread overview]
Message-ID: <20130715154050.GA5941@phenom.dumpdata.com> (raw)

Hey Linus,

I am hoping you can help me draw an understanding and a line in sand whether:
 a) Tools should not depend on /proc/config.gz to figure out whether
    a kernel has some CONFIG_X=y feature.

 b) If they are OK to do so, what do we do when certain CONFIG_X options
    get reworked/removed. Would they be considered regressions? Aka
    is this similar to 'you shall not break user-space'?


Irrespective of that, do you have any ideas of how a user-space program (say GRUB)
can figure out whether the configuration stanze it generates is supported by
the kernel. If you don't want to answer this question - since this might
open a can of worms you prefer not to deal with - that is absolutly OK.

Folks have been tossing ideas such as:
 - Let the user deal with it and if it does not boot - oh well.
 - readelf or objdump.
 - use /boot/config-<kernel>-<version> as most (all?) distros stick that in
   there.

Thanks!

             reply	other threads:[~2013-07-15 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-15 15:40 Konrad Rzeszutek Wilk [this message]
2013-07-15 17:02 ` CONFIG_* used by user-space to figure out whether a feature is on/off Greg KH
2013-07-15 17:24   ` Konrad Rzeszutek Wilk
2013-07-15 17:46     ` Linus Torvalds
2013-07-15 18:02       ` Konrad Rzeszutek Wilk
2013-07-15 18:25         ` Paul Bolle
2013-07-15 19:03           ` Konrad Rzeszutek Wilk
2013-07-15 19:13             ` Paul Bolle
2013-07-15 17:17 ` Linus Torvalds
2013-07-16  0:46   ` Raymond Jennings
2013-07-16  0:53     ` Linus Torvalds
2013-07-16  0:57       ` Raymond Jennings

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=20130715154050.GA5941@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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