5 bool "Virtual block device"
7 The User-Mode Linux port includes a driver called UBD which will let
8 you access arbitrary files on the host computer as block devices.
9 Unless you know that you do not need such virtual block devices say
12 config BLK_DEV_UBD_SYNC
13 bool "Always do synchronous disk IO for UBD"
14 depends on BLK_DEV_UBD
16 Writes to the virtual block device are not immediately written to the
17 host's disk; this may cause problems if, for example, the
18 User-Mode Linux 'Virtual Machine' uses a journalling filesystem and
19 the host computer crashes.
21 Synchronous operation (i.e. always writing data to the host's disk
22 immediately) is configurable on a per-UBD basis by using a special
23 kernel command line option. Alternatively, you can say Y here to
24 turn on synchronous operation by default for all block devices.
26 If you're running a journalling file system (like reiserfs, for
27 example) in your virtual machine, you will want to say Y here. If
28 you care for the safety of the data in your virtual machine, Y is a
29 wise choice too. In all other cases (for example, if you're just
30 playing around with User-Mode Linux) you can choose N.
32 config BLK_DEV_COW_COMMON
37 tristate "Loopback device support"
40 tristate "Network block device support"
44 tristate "RAM disk support"
46 config BLK_DEV_RAM_COUNT
47 int "Default number of RAM disks" if BLK_DEV_RAM
50 config BLK_DEV_RAM_SIZE
51 int "Default RAM disk size"
52 depends on BLK_DEV_RAM
56 bool "Initial RAM disk (initrd) support"
57 depends on BLK_DEV_RAM=y
59 #Copied directly from drivers/block/Kconfig
60 config INITRAMFS_SOURCE
61 string "Source directory of cpio_list"
64 This can be set to either a directory containing files, etc to be
65 included in the initramfs archive, or a file containing newline
68 If it is a file, it should be in the following format:
70 file <name> <location> <mode> <uid> <gid>
71 dir <name> <mode> <uid> <gid>
72 nod <name> <mode> <uid> <gid> <dev_type> <maj> <min>
75 <name> name of the file/dir/nod in the archive
76 <location> location of the file in the current filesystem
77 <mode> mode/permissions of the file
78 <uid> user id (0=root)
79 <gid> group id (0=root)
80 <dev_type> device type (b=block, c=character)
81 <maj> major number of nod
82 <min> minor number of nod
84 If you are not sure, leave it blank.
87 tristate "Example IO memory driver"
90 The User-Mode Linux port can provide support for IO Memory
91 emulation with this option. This allows a host file to be
92 specified as an I/O region on the kernel command line. That file
93 will be mapped into UML's kernel address space where a driver can
94 locate it and do whatever it wants with the memory, including
95 providing an interface to it for UML processes to use.
97 For more information, see
98 <http://user-mode-linux.sourceforge.net/iomem.html>.
100 If you'd like to be able to provide a simulated IO port space for
101 User-Mode Linux processes, say Y. If unsure, say N.
103 source "drivers/block/Kconfig.iosched"