xen/blkback: Flesh out the description in the Kconfig.
with more details. Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
This commit is contained in:
parent
b9fc02968c
commit
a4c348580e
|
@ -478,6 +478,19 @@ config XEN_BLKDEV_BACKEND
|
||||||
block devices to other guests via a high-performance shared-memory
|
block devices to other guests via a high-performance shared-memory
|
||||||
interface.
|
interface.
|
||||||
|
|
||||||
|
The corresponding Linux frontend driver is enabled by the
|
||||||
|
CONFIG_XEN_BLKDEV_FRONTEND configuration option.
|
||||||
|
|
||||||
|
The backend driver attaches itself to a any block device specified
|
||||||
|
in the XenBus configuration. There are no limits to what the block
|
||||||
|
device as long as it has a major and minor.
|
||||||
|
|
||||||
|
If you are compiling a kernel to run in a Xen block backend driver
|
||||||
|
domain (often this is domain 0) you should say Y here. To
|
||||||
|
compile this driver as a module, chose M here: the module
|
||||||
|
will be called xen-blkback.
|
||||||
|
|
||||||
|
|
||||||
config VIRTIO_BLK
|
config VIRTIO_BLK
|
||||||
tristate "Virtio block driver (EXPERIMENTAL)"
|
tristate "Virtio block driver (EXPERIMENTAL)"
|
||||||
depends on EXPERIMENTAL && VIRTIO
|
depends on EXPERIMENTAL && VIRTIO
|
||||||
|
|
Loading…
Reference in New Issue