[lkml]   [2019]   [Dec]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Why is CONFIG_VT forced on?
On Mon, Dec 30, 2019 at 06:30:15PM -0600, Rob Landley wrote:
> On x86-64 menuconfig, CONFIG_VT is forced on (in drivers->char devices->virtual
> terminal), but the help doesn't mention a "selects", and I didn't spot anything
> obvious in "find . -name 'Kconfig*' | xargs grep -rw VT".

It's forced on because of this:

config VT
bool "Virtual terminal" if EXPERT

The above is syntatic sugar for this:

prompt "Virtual terminal" if EXPERT

What this means is that the prompt is shown only if CONFIG_EXPERT is
enabled. If CONFIG_EXPERT is not set, then the default value (which
for CONFIG_VT is "yes") is used, with no way to change it.

Basically, this is because we don't want naive users to build a kernel
which displays nothing on the console; for PC class systems, 99.99% of
the time, you really do want the virtual terminal enabled.

> Congratulations, you've reinvented "come from". I'm mostly familiar with the
> kconfig plumbing from _before_ you made it turing complete: how do I navigate this?

In the case where something was actually selected, it is explained as
such when you search for that config variable. So for example, if you
run "make menuconfig", and then type '/' to search for a configuration
parameter, and then type "CONFIG_JBD2" and return. What you will see
is this:

Symbol: JBD2 [=y] │
Type : tristate │
Defined at fs/jbd2/Kconfig:2 │
Depends on: BLOCK [=y] │
Selects: CRC32 [=y] && CRYPTO [=y] && CRYPTO_CRC32C [=y] │
Selected by [y]: │
- EXT4_FS [=y] && BLOCK [=y] │
Selected by [n]: │
- EXT3_FS [=n] && BLOCK [=y] │
- OCFS2_FS [=n] && BLOCK [=y] && NET [=y] && SYSFS [=y] && CONFIGFS_FS [=y]

The values in square brackets tell you what the current value of these
configuration parameters. So it tells you that CONFIG_JBD2 is yes,
CONFIG_BLOCK is yes, EXT3_FS is no, OCFS2_FS is no, etc.

It also tells you that it is currently selected automatically because
CONFIG_BLOCK was yes, that would also cause CONFIG_JBD2 to be

And since CONFIG_JBD2 is enabled, it will force CONFIG_CRC32,
CONFIG_CRYPTO, and CONFIG_CRC32C to be selected.

It also tells you that you can find the actual definition at
fs/jbd2/Kconfig, at line #2.

> I'm guessing "stick printfs into the menuconfig binary" is the recommended next
> step for investigating this? Or is there a trick I'm missing?

See above. The menuconfig configuration parameter search feature
tells you all about how a particular CONFIG_XXX, and what dependencies
to be enabled in order for you to be able enable that parameter, and
why it might have been enabled via the select command.

What's not there is an explanation for why a parameter like CONFIG_VT
is enabled. Right now, /CONFIG_VT will display:

Symbol: VT [=y]
Type : bool
Prompt: Virtual terminal
-> Device Drivers
-> Character devices
(1) -> Enable TTY (TTY [=y])
Defined at drivers/tty/Kconfig:13
Depends on: TTY [=y] && !UML
Selects: INPUT [=y]

Now, if you look at line 13 of drivers/tty/Kconfig, you'd see:

config VT
bool "Virtual terminal" if EXPERT
depends on !UML
select INPUT
default y
If you say Y here, you will get support for terminal devices with

Perhaps it would be nice if the output of /CONFIG_VT included
something like:

Prompt requires CONFIG_EXPERT [=n], default y

I'm sure the kbuild maintainers would love to consider a patch which
did this. :-)


- Ted

 \ /
  Last update: 2019-12-31 02:55    [W:0.046 / U:0.968 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site