diff options
| -rw-r--r-- | drivers/block/Kconfig | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig index 9abb64689712..717d6e4e18d3 100644 --- a/drivers/block/Kconfig +++ b/drivers/block/Kconfig | |||
| @@ -478,6 +478,19 @@ config XEN_BLKDEV_BACKEND | |||
| 478 | block devices to other guests via a high-performance shared-memory | 478 | block devices to other guests via a high-performance shared-memory |
| 479 | interface. | 479 | interface. |
| 480 | 480 | ||
| 481 | The corresponding Linux frontend driver is enabled by the | ||
| 482 | CONFIG_XEN_BLKDEV_FRONTEND configuration option. | ||
| 483 | |||
| 484 | The backend driver attaches itself to a any block device specified | ||
| 485 | in the XenBus configuration. There are no limits to what the block | ||
| 486 | device as long as it has a major and minor. | ||
| 487 | |||
| 488 | If you are compiling a kernel to run in a Xen block backend driver | ||
| 489 | domain (often this is domain 0) you should say Y here. To | ||
| 490 | compile this driver as a module, chose M here: the module | ||
| 491 | will be called xen-blkback. | ||
| 492 | |||
| 493 | |||
| 481 | config VIRTIO_BLK | 494 | config VIRTIO_BLK |
| 482 | tristate "Virtio block driver (EXPERIMENTAL)" | 495 | tristate "Virtio block driver (EXPERIMENTAL)" |
| 483 | depends on EXPERIMENTAL && VIRTIO | 496 | depends on EXPERIMENTAL && VIRTIO |
