Block driver using virtio.
The block driver uses scatter-gather lists with sg[0] being the
request information (struct virtio_blk_outhdr) with the type, sector
and inbuf id. The next N sg entries are the bio itself, then the last
sg is the status byte. Whether the N entries are in or out depends on
whether it's a read or a write.
We accept the normal (SCSI) ioctls: they get handed through to the other
side which can then handle it or reply that it's unsupported. It's
not clear that this actually works in general, since I don't know
if blk_pc_request() requests have an accurate rq_data_dir().
Although we try to reply -ENOTTY on unsupported commands, ioctl(fd,
CDROMEJECT) returns success to userspace. This needs a separate
patch.
Signed-off-by:
Rusty Russell <rusty@rustcorp.com.au>
Cc: Jens Axboe <jens.axboe@oracle.com>
Showing
- drivers/block/Kconfig 6 additions, 0 deletionsdrivers/block/Kconfig
- drivers/block/Makefile 1 addition, 0 deletionsdrivers/block/Makefile
- drivers/block/virtio_blk.c 308 additions, 0 deletionsdrivers/block/virtio_blk.c
- include/linux/Kbuild 1 addition, 0 deletionsinclude/linux/Kbuild
- include/linux/virtio_blk.h 51 additions, 0 deletionsinclude/linux/virtio_blk.h
Please register or sign in to comment