2018-07-31 11:39:26 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
|
|
|
2018-07-31 11:39:27 +00:00
|
|
|
menu "UML-specific options"
|
|
|
|
|
|
|
|
config UML
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
select ARCH_HAS_KCOV
|
2018-07-31 11:39:32 +00:00
|
|
|
select ARCH_NO_PREEMPT
|
2018-07-31 11:39:27 +00:00
|
|
|
select HAVE_ARCH_AUDITSYSCALL
|
|
|
|
select HAVE_ARCH_SECCOMP_FILTER
|
2019-08-19 05:54:20 +00:00
|
|
|
select HAVE_ASM_MODVERSIONS
|
2018-07-31 11:39:27 +00:00
|
|
|
select HAVE_UID16
|
|
|
|
select HAVE_FUTEX_CMPXCHG if FUTEX
|
|
|
|
select HAVE_DEBUG_KMEMLEAK
|
2018-10-30 11:58:10 +00:00
|
|
|
select HAVE_DEBUG_BUGVERBOSE
|
2020-01-04 12:39:30 +00:00
|
|
|
select HAVE_COPY_THREAD_TLS
|
2018-07-31 11:39:27 +00:00
|
|
|
select GENERIC_IRQ_SHOW
|
|
|
|
select GENERIC_CPU_DEVICES
|
|
|
|
select GENERIC_CLOCKEVENTS
|
|
|
|
select HAVE_GCC_PLUGINS
|
|
|
|
select TTY # Needed for line.c
|
|
|
|
|
|
|
|
config MMU
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config NO_IOMEM
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config ISA
|
|
|
|
bool
|
|
|
|
|
|
|
|
config SBUS
|
|
|
|
bool
|
|
|
|
|
|
|
|
config TRACE_IRQFLAGS_SUPPORT
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config LOCKDEP_SUPPORT
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config STACKTRACE_SUPPORT
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
select STACKTRACE
|
|
|
|
|
|
|
|
config GENERIC_CALIBRATE_DELAY
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
|
|
|
|
config HZ
|
|
|
|
int
|
|
|
|
default 100
|
|
|
|
|
|
|
|
config NR_CPUS
|
|
|
|
int
|
|
|
|
range 1 1
|
|
|
|
default 1
|
|
|
|
|
2018-07-31 11:39:26 +00:00
|
|
|
source "arch/$(HEADER_ARCH)/um/Kconfig"
|
2018-07-31 11:39:27 +00:00
|
|
|
|
2020-01-24 22:14:01 +00:00
|
|
|
config FORBID_STATIC_LINK
|
|
|
|
bool
|
|
|
|
|
2018-07-31 11:39:27 +00:00
|
|
|
config STATIC_LINK
|
|
|
|
bool "Force a static link"
|
2020-01-24 22:14:01 +00:00
|
|
|
depends on !FORBID_STATIC_LINK
|
2018-07-31 11:39:27 +00:00
|
|
|
help
|
|
|
|
This option gives you the ability to force a static link of UML.
|
|
|
|
Normally, UML is linked as a shared binary. This is inconvenient for
|
|
|
|
use in a chroot jail. So, if you intend to run UML inside a chroot,
|
|
|
|
you probably want to say Y here.
|
|
|
|
Additionally, this option enables using higher memory spaces (up to
|
|
|
|
2.75G) for UML.
|
|
|
|
|
2020-01-24 22:14:01 +00:00
|
|
|
NOTE: This option is incompatible with some networking features which
|
|
|
|
depend on features that require being dynamically loaded (like NSS).
|
|
|
|
|
2018-07-31 11:39:27 +00:00
|
|
|
config LD_SCRIPT_STATIC
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
depends on STATIC_LINK
|
|
|
|
|
|
|
|
config LD_SCRIPT_DYN
|
|
|
|
bool
|
|
|
|
default y
|
|
|
|
depends on !LD_SCRIPT_STATIC
|
2019-03-06 21:14:55 +00:00
|
|
|
select MODULE_REL_CRCS if MODVERSIONS
|
2018-07-31 11:39:27 +00:00
|
|
|
|
|
|
|
config HOSTFS
|
|
|
|
tristate "Host filesystem"
|
|
|
|
help
|
2019-03-06 21:14:55 +00:00
|
|
|
While the User-Mode Linux port uses its own root file system for
|
|
|
|
booting and normal file access, this module lets the UML user
|
|
|
|
access files stored on the host. It does not require any
|
|
|
|
network connection between the Host and UML. An example use of
|
|
|
|
this might be:
|
2018-07-31 11:39:27 +00:00
|
|
|
|
2019-03-06 21:14:55 +00:00
|
|
|
mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
|
2018-07-31 11:39:27 +00:00
|
|
|
|
2019-03-06 21:14:55 +00:00
|
|
|
where /tmp/fromhost is an empty directory inside UML and
|
|
|
|
/tmp/umlshare is a directory on the host with files the UML user
|
|
|
|
wishes to access.
|
2018-07-31 11:39:27 +00:00
|
|
|
|
2019-03-06 21:14:55 +00:00
|
|
|
For more information, see
|
|
|
|
<http://user-mode-linux.sourceforge.net/hostfs.html>.
|
2018-07-31 11:39:27 +00:00
|
|
|
|
2019-03-06 21:14:55 +00:00
|
|
|
If you'd like to be able to work with files stored on the host,
|
|
|
|
say Y or M here; otherwise say N.
|
2018-07-31 11:39:27 +00:00
|
|
|
|
|
|
|
config MCONSOLE
|
|
|
|
bool "Management console"
|
|
|
|
depends on PROC_FS
|
|
|
|
default y
|
|
|
|
help
|
2019-03-06 21:14:55 +00:00
|
|
|
The user mode linux management console is a low-level interface to
|
|
|
|
the kernel, somewhat like the i386 SysRq interface. Since there is
|
|
|
|
a full-blown operating system running under every user mode linux
|
|
|
|
instance, there is much greater flexibility possible than with the
|
|
|
|
SysRq mechanism.
|
|
|
|
|
|
|
|
If you answer 'Y' to this option, to use this feature, you need the
|
|
|
|
mconsole client (called uml_mconsole) which is present in CVS in
|
|
|
|
2.4.5-9um and later (path /tools/mconsole), and is also in the
|
|
|
|
distribution RPM package in 2.4.6 and later.
|
|
|
|
|
|
|
|
It is safe to say 'Y' here.
|
2018-07-31 11:39:27 +00:00
|
|
|
|
|
|
|
config MAGIC_SYSRQ
|
|
|
|
bool "Magic SysRq key"
|
|
|
|
depends on MCONSOLE
|
|
|
|
help
|
|
|
|
If you say Y here, you will have some control over the system even
|
|
|
|
if the system crashes for example during kernel debugging (e.g., you
|
|
|
|
will be able to flush the buffer cache to disk, reboot the system
|
|
|
|
immediately or dump some status information). A key for each of the
|
|
|
|
possible requests is provided.
|
|
|
|
|
|
|
|
This is the feature normally accomplished by pressing a key
|
|
|
|
while holding SysRq (Alt+PrintScreen).
|
|
|
|
|
|
|
|
On UML, this is accomplished by sending a "sysrq" command with
|
|
|
|
mconsole, followed by the letter for the requested command.
|
|
|
|
|
|
|
|
The keys are documented in <file:Documentation/admin-guide/sysrq.rst>. Don't say Y
|
|
|
|
unless you really know what this hack does.
|
|
|
|
|
|
|
|
config KERNEL_STACK_ORDER
|
|
|
|
int "Kernel stack size order"
|
2019-01-04 15:38:21 +00:00
|
|
|
default 2 if 64BIT
|
|
|
|
range 2 10 if 64BIT
|
|
|
|
default 1 if !64BIT
|
2018-07-31 11:39:27 +00:00
|
|
|
help
|
|
|
|
This option determines the size of UML kernel stacks. They will
|
|
|
|
be 1 << order pages. The default is OK unless you're running Valgrind
|
|
|
|
on UML, in which case, set this to 3.
|
2019-01-04 15:38:21 +00:00
|
|
|
It is possible to reduce the stack to 1 for 64BIT and 0 for 32BIT on
|
|
|
|
older (pre-2017) CPUs. It is not recommended on newer CPUs due to the
|
|
|
|
increase in the size of the state which needs to be saved when handling
|
2019-11-20 13:36:54 +00:00
|
|
|
signals.
|
2018-07-31 11:39:27 +00:00
|
|
|
|
|
|
|
config MMAPPER
|
|
|
|
tristate "iomem emulation driver"
|
|
|
|
help
|
|
|
|
This driver allows a host file to be used as emulated IO memory inside
|
|
|
|
UML.
|
|
|
|
|
|
|
|
config NO_DMA
|
|
|
|
def_bool y
|
|
|
|
|
|
|
|
config PGTABLE_LEVELS
|
|
|
|
int
|
|
|
|
default 3 if 3_LEVEL_PGTABLES
|
|
|
|
default 2
|
|
|
|
|
|
|
|
config SECCOMP
|
|
|
|
def_bool y
|
|
|
|
prompt "Enable seccomp to safely compute untrusted bytecode"
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2018-07-31 11:39:27 +00:00
|
|
|
This kernel feature is useful for number crunching applications
|
|
|
|
that may need to compute untrusted bytecode during their
|
|
|
|
execution. By using pipes or other transports made available to
|
|
|
|
the process as file descriptors supporting the read/write
|
|
|
|
syscalls, it's possible to isolate those applications in
|
|
|
|
their own address space using seccomp. Once seccomp is
|
|
|
|
enabled via prctl(PR_SET_SECCOMP), it cannot be disabled
|
|
|
|
and the task is only allowed to execute a few safe syscalls
|
|
|
|
defined by each seccomp mode.
|
|
|
|
|
|
|
|
If unsure, say Y.
|
|
|
|
|
2019-05-27 08:34:27 +00:00
|
|
|
config UML_TIME_TRAVEL_SUPPORT
|
|
|
|
bool
|
|
|
|
prompt "Support time-travel mode (e.g. for test execution)"
|
2019-12-13 09:01:28 +00:00
|
|
|
# inf-cpu mode is incompatible with the benchmarking
|
|
|
|
depends on !RAID6_PQ_BENCHMARK
|
um: time-travel: Rewrite as an event scheduler
Instead of tracking all the various timer configurations,
modify the time-travel mode to have an event scheduler and
use a timer event on the scheduler to handle the different
timer configurations.
This doesn't change the function right now, but it prepares
the code for having different kinds of events in the future
(i.e. interrupts coming from other devices that are part of
co-simulation.)
While at it, also move time_travel_sleep() to time.c to
reduce the externally visible API surface.
Also, we really should mark time-travel as incompatible with
SMP, even if UML doesn't support SMP yet.
Finally, I noticed a bug while developing this - if we move
time forward due to consuming time while reading the clock,
we might move across the next event and that would cause us
to go backward in time when we then handle that event. Fix
that by invoking the whole event machine in this case, but
in order to simplify this, make reading the clock only cost
something when interrupts are not disabled. Otherwise, we'd
have to hook into the interrupt delivery machinery etc. and
that's somewhat intrusive.
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Signed-off-by: Richard Weinberger <richard@nod.at>
2020-02-13 13:26:45 +00:00
|
|
|
depends on !SMP
|
2019-05-27 08:34:27 +00:00
|
|
|
help
|
|
|
|
Enable this option to support time travel inside the UML instance.
|
|
|
|
|
|
|
|
After enabling this option, two modes are accessible at runtime
|
|
|
|
(selected by the kernel command line), see the kernel's command-
|
|
|
|
line help for more details.
|
|
|
|
|
|
|
|
It is safe to say Y, but you probably don't need this.
|
|
|
|
|
2018-07-31 11:39:27 +00:00
|
|
|
endmenu
|
|
|
|
|
2018-07-31 11:39:28 +00:00
|
|
|
source "arch/um/drivers/Kconfig"
|