diff options
| author | Kevin Wolf <kwolf@redhat.com> | 2016-03-04 14:28:01 +0100 |
|---|---|---|
| committer | Timothy Pearson <tpearson@raptorengineering.com> | 2019-11-29 20:01:34 -0600 |
| commit | cdc4827286034b63ae84ad34f762133a698915f7 (patch) | |
| tree | 3075061d8701a9a1e796372456fc40f8a60c0bbe /include/block/block_int.h | |
| parent | a0dba62b0ca3070700e713580a3c6765130d448a (diff) | |
| download | hqemu-cdc4827286034b63ae84ad34f762133a698915f7.zip hqemu-cdc4827286034b63ae84ad34f762133a698915f7.tar.gz | |
block: Move enable_write_cache to BB level
Whether a write cache is used or not is a decision that concerns the
user (e.g. the guest device) rather than the backend. It was already
logically part of the BB level as bdrv_move_feature_fields() always kept
it on top of the BDS tree; with this patch, the core of it (the actual
flag and the additional flushes) is also implemented there.
Direct callers of bdrv_open() must pass BDRV_O_CACHE_WB now if bs
doesn't have a BlockBackend attached.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
Diffstat (limited to 'include/block/block_int.h')
| -rw-r--r-- | include/block/block_int.h | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/include/block/block_int.h b/include/block/block_int.h index 1177c25..4884609 100644 --- a/include/block/block_int.h +++ b/include/block/block_int.h @@ -442,9 +442,6 @@ struct BlockDriverState { /* Alignment requirement for offset/length of I/O requests */ unsigned int request_alignment; - /* do we need to tell the quest if we have a volatile write cache? */ - int enable_write_cache; - /* the following member gives a name to every node on the bs graph. */ char node_name[32]; /* element of the list of named nodes building the graph */ |
