diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2016-03-18 17:46:45 +0100 |
|---|---|---|
| committer | Timothy Pearson <tpearson@raptorengineering.com> | 2019-11-29 20:01:34 -0600 |
| commit | 58105bc517c45b8b910edcec9697886fc8b8fef8 (patch) | |
| tree | 544cb2daa60361e0e17fc4cf69c61f8a05a7cee5 /qemu-io-cmds.c | |
| parent | 225fbeb4b1b757254d60f98c768db758f3c2228e (diff) | |
| download | hqemu-58105bc517c45b8b910edcec9697886fc8b8fef8.zip hqemu-58105bc517c45b8b910edcec9697886fc8b8fef8.tar.gz | |
block: Remove BDRV_O_CACHE_WB
The previous patches have successively made blk->enable_write_cache the
true source for the information whether a writethrough mode must be
implemented. The corresponding BDRV_O_CACHE_WB is only useless baggage
we're carrying around, so now's the time to remove it.
At the same time, we remove the 'cache.writeback' option parsing on the
BDS level as the only effect was setting the BDRV_O_CACHE_WB flag.
This change requires test cases that explicitly enabled the option to
drop it. Other than that and the change of the error message when
writethrough is enabled on the BDS level (from "Can't set writethrough
mode" to "doesn't support the option"), there should be no change in
behaviour.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'qemu-io-cmds.c')
| -rw-r--r-- | qemu-io-cmds.c | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/qemu-io-cmds.c b/qemu-io-cmds.c index 932e367..382faa8 100644 --- a/qemu-io-cmds.c +++ b/qemu-io-cmds.c @@ -2151,7 +2151,6 @@ static int reopen_f(BlockBackend *blk, int argc, char **argv) opts = qopts ? qemu_opts_to_qdict(qopts, NULL) : NULL; qemu_opts_reset(&reopen_opts); - flags |= blk_enable_write_cache(blk) ? BDRV_O_CACHE_WB : 0; brq = bdrv_reopen_queue(NULL, bs, opts, flags); bdrv_reopen_multiple(brq, &local_err); if (local_err) { |
