[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices
|
From: |
Kevin Wolf |
|
Subject: |
Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices |
|
Date: |
Mon, 27 Jun 2016 18:38:52 +0200 |
|
User-agent: |
Mutt/1.5.21 (2010-09-15) |
Am 27.06.2016 um 18:13 hat Max Reitz geschrieben:
> I'm not sure if WCE truly is a guest device property, but adding it as a
> guest device property and then syncing it to the BB makes sense (as done
> in patch 7).
It is truly a guest device property. Physical hardware can have a
volatile write cache and software can actively enable or disable it. We
support this in all relevant guest devices (SCSI, virtio-blk, IDE).
Kevin
pgp9yqZgvfPCr.pgp
Description: PGP signature
- Re: [Qemu-devel] [RFC PATCH 2/7] block: Add blk_by_dev(), (continued)
- [Qemu-devel] [RFC PATCH 5/7] block: Accept device model name for blockdev-open/close-tray, Kevin Wolf, 2016/06/23
- [Qemu-devel] [RFC PATCH 7/7] block/qdev: Allow configuring WCE with qdev properties, Kevin Wolf, 2016/06/23
- [Qemu-devel] [RFC PATCH 6/7] block: Accept node-name for block-stream, Kevin Wolf, 2016/06/23
- Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices, Paolo Bonzini, 2016/06/23
- Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices, Max Reitz, 2016/06/27
- Re: [Qemu-devel] [RFC PATCH 0/7] BlockBackends, nodes and guest devices,
Kevin Wolf <=