1config STATIC_LINK
  2	bool "Force a static link"
  3	default n
  4	help
  5	  This option gives you the ability to force a static link of UML.
  6	  Normally, UML is linked as a shared binary.  This is inconvenient for
  7	  use in a chroot jail.  So, if you intend to run UML inside a chroot,
  8	  you probably want to say Y here.
  9	  Additionally, this option enables using higher memory spaces (up to
 10	  2.75G) for UML.
 11
 12source "mm/Kconfig"
 
 13
 14config LD_SCRIPT_STATIC
 15	bool
 16	default y
 17	depends on STATIC_LINK
 18
 19config LD_SCRIPT_DYN
 20	bool
 21	default y
 22	depends on !LD_SCRIPT_STATIC
 23
 24source "fs/Kconfig.binfmt"
 25
 26config HOSTFS
 27	tristate "Host filesystem"
 28	help
 29          While the User-Mode Linux port uses its own root file system for
 30          booting and normal file access, this module lets the UML user
 31          access files stored on the host.  It does not require any
 32          network connection between the Host and UML.  An example use of
 33          this might be:
 34
 35          mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
 36
 37          where /tmp/fromhost is an empty directory inside UML and
 38          /tmp/umlshare is a directory on the host with files the UML user
 39          wishes to access.
 40
 41          For more information, see
 42          <http://user-mode-linux.sourceforge.net/hostfs.html>.
 43
 44          If you'd like to be able to work with files stored on the host,
 45          say Y or M here; otherwise say N.
 46
 47config HPPFS
 48	tristate "HoneyPot ProcFS (EXPERIMENTAL)"
 49	depends on EXPERIMENTAL && PROC_FS
 50	help
 51	  hppfs (HoneyPot ProcFS) is a filesystem which allows UML /proc
 52	  entries to be overridden, removed, or fabricated from the host.
 53	  Its purpose is to allow a UML to appear to be a physical machine
 54	  by removing or changing anything in /proc which gives away the
 55	  identity of a UML.
 56
 57	  See <http://user-mode-linux.sf.net/old/hppfs.html> for more information.
 58
 59	  You only need this if you are setting up a UML honeypot.  Otherwise,
 60	  it is safe to say 'N' here.
 61
 62config MCONSOLE
 63	bool "Management console"
 64	default y
 65	help
 66          The user mode linux management console is a low-level interface to
 67          the kernel, somewhat like the i386 SysRq interface.  Since there is
 68          a full-blown operating system running under every user mode linux
 69          instance, there is much greater flexibility possible than with the
 70          SysRq mechanism.
 71
 72          If you answer 'Y' to this option, to use this feature, you need the
 73          mconsole client (called uml_mconsole) which is present in CVS in
 74          2.4.5-9um and later (path /tools/mconsole), and is also in the
 75          distribution RPM package in 2.4.6 and later.
 76
 77          It is safe to say 'Y' here.
 78
 79config MAGIC_SYSRQ
 80	bool "Magic SysRq key"
 81	depends on MCONSOLE
 82	help
 83	  If you say Y here, you will have some control over the system even
 84	  if the system crashes for example during kernel debugging (e.g., you
 85	  will be able to flush the buffer cache to disk, reboot the system
 86	  immediately or dump some status information). A key for each of the
 87	  possible requests is provided.
 88
 89	  This is the feature normally accomplished by pressing a key
 90	  while holding SysRq (Alt+PrintScreen).
 91
 92	  On UML, this is accomplished by sending a "sysrq" command with
 93	  mconsole, followed by the letter for the requested command.
 94
 95	  The keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
 96	  unless you really know what this hack does.
 97
 98config SMP
 99	bool "Symmetric multi-processing support (EXPERIMENTAL)"
100	default n
101	depends on BROKEN
102	help
103	  This option enables UML SMP support.
104	  It is NOT related to having a real SMP box. Not directly, at least.
105
106	  UML implements virtual SMP by allowing as many processes to run
107	  simultaneously on the host as there are virtual processors configured.
108
109	  Obviously, if the host is a uniprocessor, those processes will
110	  timeshare, but, inside UML, will appear to be running simultaneously.
111	  If the host is a multiprocessor, then UML processes may run
112	  simultaneously, depending on the host scheduler.
113
114	  This, however, is supported only in TT mode. So, if you use the SKAS
115	  patch on your host, switching to TT mode and enabling SMP usually
116	  gives	you worse performances.
117	  Also, since the support for SMP has been under-developed, there could
118	  be some bugs being exposed by enabling SMP.
119
120	  If you don't know what to do, say N.
121
122config NR_CPUS
123	int "Maximum number of CPUs (2-32)"
124	range 2 32
125	depends on SMP
126	default "32"
127
128config HIGHMEM
129	bool "Highmem support (EXPERIMENTAL)"
130	depends on !64BIT && BROKEN
131	default n
132	help
133	  This was used to allow UML to run with big amounts of memory.
134	  Currently it is unstable, so if unsure say N.
135
136	  To use big amounts of memory, it is recommended enable static
137	  linking (i.e. CONFIG_STATIC_LINK) - this should allow the
138	  guest to use up to 2.75G of memory.
139
140config KERNEL_STACK_ORDER
141	int "Kernel stack size order"
142	default 1 if 64BIT
143	range 1 10 if 64BIT
144	default 0 if !64BIT
145	help
146	  This option determines the size of UML kernel stacks.  They will
147	  be 1 << order pages.  The default is OK unless you're running Valgrind
148	  on UML, in which case, set this to 3.
149
150config MMAPPER
151	tristate "iomem emulation driver"
152	help
153	  This driver allows a host file to be used as emulated IO memory inside
154	  UML.
155
156config NO_DMA
157	def_bool y

  1config STATIC_LINK
  2	bool "Force a static link"
  3	default n
  4	help
  5	  This option gives you the ability to force a static link of UML.
  6	  Normally, UML is linked as a shared binary.  This is inconvenient for
  7	  use in a chroot jail.  So, if you intend to run UML inside a chroot,
  8	  you probably want to say Y here.
  9	  Additionally, this option enables using higher memory spaces (up to
 10	  2.75G) for UML.
 11
 12source "mm/Kconfig"
 13source "kernel/time/Kconfig"
 14
 15config LD_SCRIPT_STATIC
 16	bool
 17	default y
 18	depends on STATIC_LINK
 19
 20config LD_SCRIPT_DYN
 21	bool
 22	default y
 23	depends on !LD_SCRIPT_STATIC
 24
 25source "fs/Kconfig.binfmt"
 26
 27config HOSTFS
 28	tristate "Host filesystem"
 29	help
 30          While the User-Mode Linux port uses its own root file system for
 31          booting and normal file access, this module lets the UML user
 32          access files stored on the host.  It does not require any
 33          network connection between the Host and UML.  An example use of
 34          this might be:
 35
 36          mount none /tmp/fromhost -t hostfs -o /tmp/umlshare
 37
 38          where /tmp/fromhost is an empty directory inside UML and
 39          /tmp/umlshare is a directory on the host with files the UML user
 40          wishes to access.
 41
 42          For more information, see
 43          <http://user-mode-linux.sourceforge.net/hostfs.html>.
 44
 45          If you'd like to be able to work with files stored on the host,
 46          say Y or M here; otherwise say N.
 47
 48config HPPFS
 49	tristate "HoneyPot ProcFS (EXPERIMENTAL)"
 50	depends on EXPERIMENTAL && PROC_FS
 51	help
 52	  hppfs (HoneyPot ProcFS) is a filesystem which allows UML /proc
 53	  entries to be overridden, removed, or fabricated from the host.
 54	  Its purpose is to allow a UML to appear to be a physical machine
 55	  by removing or changing anything in /proc which gives away the
 56	  identity of a UML.
 57
 58	  See <http://user-mode-linux.sf.net/old/hppfs.html> for more information.
 59
 60	  You only need this if you are setting up a UML honeypot.  Otherwise,
 61	  it is safe to say 'N' here.
 62
 63config MCONSOLE
 64	bool "Management console"
 65	default y
 66	help
 67          The user mode linux management console is a low-level interface to
 68          the kernel, somewhat like the i386 SysRq interface.  Since there is
 69          a full-blown operating system running under every user mode linux
 70          instance, there is much greater flexibility possible than with the
 71          SysRq mechanism.
 72
 73          If you answer 'Y' to this option, to use this feature, you need the
 74          mconsole client (called uml_mconsole) which is present in CVS in
 75          2.4.5-9um and later (path /tools/mconsole), and is also in the
 76          distribution RPM package in 2.4.6 and later.
 77
 78          It is safe to say 'Y' here.
 79
 80config MAGIC_SYSRQ
 81	bool "Magic SysRq key"
 82	depends on MCONSOLE
 83	help
 84	  If you say Y here, you will have some control over the system even
 85	  if the system crashes for example during kernel debugging (e.g., you
 86	  will be able to flush the buffer cache to disk, reboot the system
 87	  immediately or dump some status information). A key for each of the
 88	  possible requests is provided.
 89
 90	  This is the feature normally accomplished by pressing a key
 91	  while holding SysRq (Alt+PrintScreen).
 92
 93	  On UML, this is accomplished by sending a "sysrq" command with
 94	  mconsole, followed by the letter for the requested command.
 95
 96	  The keys are documented in <file:Documentation/sysrq.txt>. Don't say Y
 97	  unless you really know what this hack does.
 98
 99config SMP
100	bool "Symmetric multi-processing support (EXPERIMENTAL)"
101	default n
102	depends on BROKEN
103	help
104	  This option enables UML SMP support.
105	  It is NOT related to having a real SMP box. Not directly, at least.
106
107	  UML implements virtual SMP by allowing as many processes to run
108	  simultaneously on the host as there are virtual processors configured.
109
110	  Obviously, if the host is a uniprocessor, those processes will
111	  timeshare, but, inside UML, will appear to be running simultaneously.
112	  If the host is a multiprocessor, then UML processes may run
113	  simultaneously, depending on the host scheduler.
114
115	  This, however, is supported only in TT mode. So, if you use the SKAS
116	  patch on your host, switching to TT mode and enabling SMP usually
117	  gives	you worse performances.
118	  Also, since the support for SMP has been under-developed, there could
119	  be some bugs being exposed by enabling SMP.
120
121	  If you don't know what to do, say N.
122
123config NR_CPUS
124	int "Maximum number of CPUs (2-32)"
125	range 2 32
126	depends on SMP
127	default "32"
128
129config HIGHMEM
130	bool "Highmem support (EXPERIMENTAL)"
131	depends on !64BIT && BROKEN
132	default n
133	help
134	  This was used to allow UML to run with big amounts of memory.
135	  Currently it is unstable, so if unsure say N.
136
137	  To use big amounts of memory, it is recommended enable static
138	  linking (i.e. CONFIG_STATIC_LINK) - this should allow the
139	  guest to use up to 2.75G of memory.
140
141config KERNEL_STACK_ORDER
142	int "Kernel stack size order"
143	default 1 if 64BIT
144	range 1 10 if 64BIT
145	default 0 if !64BIT
146	help
147	  This option determines the size of UML kernel stacks.  They will
148	  be 1 << order pages.  The default is OK unless you're running Valgrind
149	  on UML, in which case, set this to 3.
 
 
 
 
 
 
150
151config NO_DMA
152	def_bool y