2008-12-04 20:52:44 +01:00
|
|
|
/*
|
|
|
|
* Virtio Block Device
|
|
|
|
*
|
|
|
|
* Copyright IBM, Corp. 2007
|
|
|
|
*
|
|
|
|
* Authors:
|
|
|
|
* Anthony Liguori <aliguori@us.ibm.com>
|
|
|
|
*
|
|
|
|
* This work is licensed under the terms of the GNU GPL, version 2. See
|
|
|
|
* the COPYING file in the top-level directory.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
|
2016-06-29 13:47:03 +02:00
|
|
|
#ifndef QEMU_VIRTIO_BLK_H
|
|
|
|
#define QEMU_VIRTIO_BLK_H
|
2008-12-04 20:52:44 +01:00
|
|
|
|
2015-02-16 22:36:03 +01:00
|
|
|
#include "standard-headers/linux/virtio_blk.h"
|
2013-02-05 17:06:20 +01:00
|
|
|
#include "hw/virtio/virtio.h"
|
|
|
|
#include "hw/block/block.h"
|
2014-03-03 11:30:08 +01:00
|
|
|
#include "sysemu/iothread.h"
|
2014-10-07 13:59:18 +02:00
|
|
|
#include "sysemu/block-backend.h"
|
2008-12-04 20:52:44 +01:00
|
|
|
|
2013-04-09 12:04:48 +02:00
|
|
|
#define TYPE_VIRTIO_BLK "virtio-blk-device"
|
2013-03-18 17:37:22 +01:00
|
|
|
#define VIRTIO_BLK(obj) \
|
|
|
|
OBJECT_CHECK(VirtIOBlock, (obj), TYPE_VIRTIO_BLK)
|
|
|
|
|
2009-04-23 12:58:51 +02:00
|
|
|
/* This is the last element of the write scatter-gather list */
|
2008-12-04 20:52:44 +01:00
|
|
|
struct virtio_blk_inhdr
|
|
|
|
{
|
|
|
|
unsigned char status;
|
|
|
|
};
|
|
|
|
|
2012-05-16 12:54:05 +02:00
|
|
|
struct VirtIOBlkConf
|
|
|
|
{
|
|
|
|
BlockConf conf;
|
2014-03-03 11:30:08 +01:00
|
|
|
IOThread *iothread;
|
2012-05-16 12:54:05 +02:00
|
|
|
char *serial;
|
virtio-blk: always enable VIRTIO_BLK_F_SCSI
VIRTIO_BLK_F_SCSI is supposed to mean whether the host can *parse*
SCSI requests, not *execute* them. You could run QEMU with scsi=on
and a file-backed disk, and QEMU would fail all SCSI requests even
though it advertises VIRTIO_BLK_F_SCSI.
Because we need to do this to fix a migration compatibility problem
related to how QEMU is invoked by management, we must do this
unconditionally even on older machine types. This more or less assumes
that no one ever invoked QEMU with scsi=off.
Here is how testing goes:
- old QEMU, scsi=on -> new QEMU, scsi=on
- new QEMU, scsi=on -> old QEMU, scsi=on
- old QEMU, scsi=off -> new QEMU, scsi=on
- new QEMU, scsi=off -> old QEMU, scsi=on
ok (new QEMU has VIRTIO_BLK_F_SCSI, adding host features is fine)
- old QEMU, scsi=off -> new QEMU, scsi=off
ok (new QEMU has VIRTIO_BLK_F_SCSI, adding host features is fine)
- old QEMU, scsi=on -> new QEMU, scsi=off
ok, bug fixed
- new QEMU, scsi=on -> old QEMU, scsi=off
doesn't work (same as: old QEMU, scsi=on -> old QEMU, scsi=off)
- new QEMU, scsi=off -> old QEMU, scsi=off
broken by the patch
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
2012-05-16 12:54:06 +02:00
|
|
|
uint32_t scsi;
|
2012-12-10 13:14:39 +01:00
|
|
|
uint32_t config_wce;
|
2015-02-02 14:52:22 +01:00
|
|
|
uint32_t request_merging;
|
2016-06-21 14:13:10 +02:00
|
|
|
uint16_t num_queues;
|
2012-05-16 12:54:05 +02:00
|
|
|
};
|
|
|
|
|
2013-02-05 17:06:20 +01:00
|
|
|
struct VirtIOBlockDataPlane;
|
|
|
|
|
2014-06-17 08:32:06 +02:00
|
|
|
struct VirtIOBlockReq;
|
2013-03-18 17:37:18 +01:00
|
|
|
typedef struct VirtIOBlock {
|
2013-03-18 17:37:27 +01:00
|
|
|
VirtIODevice parent_obj;
|
2014-10-07 13:59:18 +02:00
|
|
|
BlockBackend *blk;
|
2013-03-18 17:37:18 +01:00
|
|
|
void *rq;
|
|
|
|
QEMUBH *bh;
|
2014-10-07 13:59:17 +02:00
|
|
|
VirtIOBlkConf conf;
|
2013-03-18 17:37:18 +01:00
|
|
|
unsigned short sector_mask;
|
virtio-blk: do not relay a previous driver's WCE configuration to the current
The following sequence happens:
- the SeaBIOS virtio-blk driver does not support the WCE feature, which
causes QEMU to disable writeback caching
- the Linux virtio-blk driver resets the device, finds WCE is available
but writeback caching is disabled; tells block layer to not send cache
flush commands
- the Linux virtio-blk driver sets the DRIVER_OK bit, which causes
writeback caching to be re-enabled, but the Linux virtio-blk driver does
not know of this side effect and cache flushes remain disabled
The bug is at the third step. If the guest does know about CONFIG_WCE,
QEMU should ignore the WCE feature's state. The guest will control the
cache mode solely using configuration space. This change makes Linux
do flushes correctly, but Linux will keep SeaBIOS's writethrough mode.
Hence, whenever the guest is reset, the cache mode of the disk should
be reset to whatever was specified in the "-drive" option. With this
change, the Linux virtio-blk driver finds that writeback caching is
enabled, and tells the block layer to send cache flush commands
appropriately.
Reported-by: Rusty Russell <rusty@au1.ibm.com
Cc: qemu-stable@nongnu.org
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2013-09-20 17:31:55 +02:00
|
|
|
bool original_wce;
|
2013-03-18 17:37:18 +01:00
|
|
|
VMChangeStateEntry *change;
|
2016-04-06 12:16:23 +02:00
|
|
|
bool dataplane_disabled;
|
virtio-blk: fix "disabled data plane" mode
In disabled mode, virtio-blk dataplane seems to be enabled, but flow
actually goes through the normal virtio path. This patch simplifies a bit
the handling of disabled mode. In disabled mode, virtio_blk_handle_output
might be called even if s->dataplane is not NULL.
This is a bit tricky, because the current check for s->dataplane will
always trigger, causing a continuous stream of calls to
virtio_blk_data_plane_start. Unfortunately, these calls will not
do anything. To fix this, set the "started" flag even in disabled
mode, and skip virtio_blk_data_plane_start if the started flag is true.
The resulting changes also prepare the code for the next patch, were
virtio-blk dataplane will reuse the same virtio_blk_handle_output function
as "regular" virtio-blk.
Because struct VirtIOBlockDataPlane is opaque in virtio-blk.c, we have
to move s->dataplane->started inside struct VirtIOBlock.
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
Acked-by: Stefan Hajnoczi <stefanha@redhat.com>
2016-02-14 18:17:08 +01:00
|
|
|
bool dataplane_started;
|
2013-02-05 17:06:20 +01:00
|
|
|
struct VirtIOBlockDataPlane *dataplane;
|
2013-03-18 17:37:18 +01:00
|
|
|
} VirtIOBlock;
|
|
|
|
|
2014-06-11 06:11:42 +02:00
|
|
|
typedef struct VirtIOBlockReq {
|
2016-01-31 11:28:57 +01:00
|
|
|
VirtQueueElement elem;
|
2015-02-02 14:52:21 +01:00
|
|
|
int64_t sector_num;
|
2014-06-11 06:11:42 +02:00
|
|
|
VirtIOBlock *dev;
|
2016-06-21 14:13:13 +02:00
|
|
|
VirtQueue *vq;
|
2014-06-11 06:11:42 +02:00
|
|
|
struct virtio_blk_inhdr *in;
|
2014-06-11 06:11:48 +02:00
|
|
|
struct virtio_blk_outhdr out;
|
2014-06-11 06:11:42 +02:00
|
|
|
QEMUIOVector qiov;
|
2015-04-02 19:50:44 +02:00
|
|
|
size_t in_len;
|
2014-06-11 06:11:42 +02:00
|
|
|
struct VirtIOBlockReq *next;
|
2015-02-02 14:52:21 +01:00
|
|
|
struct VirtIOBlockReq *mr_next;
|
2014-06-11 06:11:42 +02:00
|
|
|
BlockAcctCookie acct;
|
|
|
|
} VirtIOBlockReq;
|
|
|
|
|
2015-02-02 14:52:21 +01:00
|
|
|
#define VIRTIO_BLK_MAX_MERGE_REQS 32
|
|
|
|
|
|
|
|
typedef struct MultiReqBuffer {
|
|
|
|
VirtIOBlockReq *reqs[VIRTIO_BLK_MAX_MERGE_REQS];
|
|
|
|
unsigned int num_reqs;
|
|
|
|
bool is_write;
|
|
|
|
} MultiReqBuffer;
|
|
|
|
|
2017-02-09 09:40:47 +01:00
|
|
|
bool virtio_blk_handle_vq(VirtIOBlock *s, VirtQueue *vq);
|
2016-04-06 12:16:26 +02:00
|
|
|
|
2008-12-04 20:52:44 +01:00
|
|
|
#endif
|