RFC allow guest control of the volatile write cache
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest4 patches 12 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | block: clarify the meaning of BDRV_O_NOCACHEblock.c block/ block/ +3 more | +12 | 6 replies | |
| 2/4 | block: add a helper to change writeback mode on the flyblock.c block.h | +41 | 6 replies | |
| 3/4 | ide: wire up setfeatures cache controlhw/ | +17 | 0 replies | |
| 4/4 | virtio-blk: add runtime cache controlhw/ hw/ | +24 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Qemu-devel] [PATCH, RFC 0/4] allow guest control of the volatile write cache
This series adds support for the guest to control the volatile write cache setting on disks exported by qemu for ide and virtio. For ide it just wires up the existing SETFEATURES calls, and for virtio it adds a new writeable config space field. SCSI is not supported at this point, as the convoluted callback mess in the SCSI stack doesn't allow commands except for plain WRITEs to read data from guest memory.
The backend is based on the code that Prerna posted a while ago, and not Stefan's /proc based variant. I'm open to either one, but the problem with the /proc based one is that it's Linux-specific.