diff options
author | John Snow <jsnow@redhat.com> | 2019-03-12 12:05:48 -0400 |
---|---|---|
committer | John Snow <jsnow@redhat.com> | 2019-03-12 12:05:48 -0400 |
commit | 50a47257f8f1368ba08e4789bb63ca84c4306dde (patch) | |
tree | 062bde9667c81555e2df724d2df69a173bd91997 /.travis.yml | |
parent | 4db6ceb0b594e179fcbd46a351b8cebaa840bf0d (diff) | |
download | qemu-50a47257f8f1368ba08e4789bb63ca84c4306dde.zip qemu-50a47257f8f1368ba08e4789bb63ca84c4306dde.tar.gz qemu-50a47257f8f1368ba08e4789bb63ca84c4306dde.tar.bz2 |
block/dirty-bitmaps: rename frozen predicate helper
"Frozen" was a good description a long time ago, but it isn't adequate now.
Rename the frozen predicate to has_successor to make the semantics of the
predicate more clear to outside callers.
In the process, remove some calls to frozen() that no longer semantically
make sense. For bdrv_enable_dirty_bitmap_locked and
bdrv_disable_dirty_bitmap_locked, it doesn't make sense to prohibit QEMU
internals from performing this action when we only wished to prohibit QMP
users from issuing these commands. All of the QMP API commands for bitmap
manipulation already check against user_locked() to prohibit these actions.
Several other assertions really want to check that the bitmap isn't in-use
by another operation -- use the bitmap_user_locked function for this instead,
which presently also checks for has_successor. This leaves some redundant
checks of has_successor through different helpers that are addressed in
forthcoming patches.
Signed-off-by: John Snow <jsnow@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Message-id: 20190223000614.13894-3-jsnow@redhat.com
Signed-off-by: John Snow <jsnow@redhat.com>
Diffstat (limited to '.travis.yml')
0 files changed, 0 insertions, 0 deletions