qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Fam Zheng <famz@redhat.com>, John Snow <jsnow@redhat.com>
Subject: [Qemu-devel] [PATCH for-2.9 0/2] hbitmap: Add hbitmap_is_serializable()
Date: Tue, 15 Nov 2016 23:57:44 +0100	[thread overview]
Message-ID: <20161115225746.3590-1-mreitz@redhat.com> (raw)

This series is a follow-up for "hbitmap: Fix shifts of constants by
granularity".

So far, adding the assertion in hbitmap_serialization_granularity() (as
done by said previous patch) is enough and we know that it will always
hold true since bitmaps are only serialized as part of a test for now.

However, in the future we need some other way than a failed assertion to
tell the user that they cannot serialize a certain bitmap. This series
adds a function that can be called to tell whether a bitmap can be
(de-)serialized.


Max Reitz (2):
  hbitmap: Add hbitmap_is_serializable()
  test-hbitmap: Add hbitmap_is_serializable() calls

 include/qemu/hbitmap.h | 13 +++++++++++++
 tests/test-hbitmap.c   | 11 +++++++++++
 util/hbitmap.c         | 22 +++++++++++++++++++---
 3 files changed, 43 insertions(+), 3 deletions(-)

-- 
2.10.2

             reply	other threads:[~2016-11-15 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 22:57 Max Reitz [this message]
2016-11-15 22:57 ` [Qemu-devel] [PATCH for-2.9 1/2] hbitmap: Add hbitmap_is_serializable() Max Reitz
2016-11-15 22:57 ` [Qemu-devel] [PATCH for-2.9 2/2] test-hbitmap: Add hbitmap_is_serializable() calls Max Reitz
2016-11-17 10:36 ` [Qemu-devel] [Qemu-block] [PATCH for-2.9 0/2] hbitmap: Add hbitmap_is_serializable() Stefan Hajnoczi
2017-01-23 18:49 ` [Qemu-devel] " Max Reitz
2017-01-24  2:15 ` Fam Zheng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161115225746.3590-1-mreitz@redhat.com \
    --to=mreitz@redhat.com \
    --cc=famz@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).