Blame view

kernel/linux-rt-4.4.41/arch/um/Kconfig.um 3.35 KB
5113f6f70   김현기   kernel add
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
  config STATIC_LINK
  	bool "Force a static link"
  	default n
  	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.
  
  source "mm/Kconfig"
  
  config LD_SCRIPT_STATIC
  	bool
  	default y
  	depends on STATIC_LINK
  
  config LD_SCRIPT_DYN
  	bool
  	default y
  	depends on !LD_SCRIPT_STATIC
  
  source "fs/Kconfig.binfmt"
  
  config HOSTFS
  	tristate "Host filesystem"
  	help
            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:
  
            mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
  
            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.
  
            For more information, see
            <http://user-mode-linux.sourceforge.net/hostfs.html>.
  
            If you'd like to be able to work with files stored on the host,
            say Y or M here; otherwise say N.
  
  config MCONSOLE
  	bool "Management console"
  	depends on PROC_FS
  	default y
  	help
            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.
  
  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/sysrq.txt>. Don't say Y
  	  unless you really know what this hack does.
  
  config KERNEL_STACK_ORDER
  	int "Kernel stack size order"
  	default 1 if 64BIT
  	range 1 10 if 64BIT
  	default 0 if !64BIT
  	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.
  
  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