From: Fam Zheng <famz@redhat.com>
To: John Snow <jsnow@redhat.com>
Cc: kwolf@redhat.com,
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
stefanha@redhat.com, den@openvz.org
Subject: Re: [Qemu-devel] [PATCH v4 RFC] spec: add qcow2-dirty-bitmaps specification
Date: Tue, 15 Dec 2015 12:34:47 +0800 [thread overview]
Message-ID: <20151215043447.GC19034@ad.usersys.redhat.com> (raw)
In-Reply-To: <566F4210.1020200@redhat.com>
On Mon, 12/14 17:26, John Snow wrote:
>
> If the auto bit is on, it's a must.
>
> Let's try again:
>
> "1: auto
> This bitmap is of the Dirty Tracking Type and must accurately
> reflect all writes to the virtual disk image by any application
> that would write to it. This bitmap should not lose the auto bit
> except by user intervention."
>
> Or something like that? The idea is that it will indeed be "autoloaded"
> and made active, but some bitmaps might be stored in various
> frozen/unactive states where this is not desirable.
Yes, I like this idea. It also answers my "enabled" flag question in reply to
Max's comments.
Fam
next prev parent reply other threads:[~2015-12-15 4:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 17:43 [Qemu-devel] [PATCH v4 RFC] spec: add qcow2-dirty-bitmaps specification Vladimir Sementsov-Ogievskiy
2015-12-14 20:05 ` Max Reitz
2015-12-14 20:45 ` John Snow
2015-12-14 21:44 ` Max Reitz
2015-12-14 22:26 ` John Snow
2015-12-15 4:34 ` Fam Zheng [this message]
2015-12-15 14:10 ` Max Reitz
2015-12-21 13:41 ` Vladimir Sementsov-Ogievskiy
2015-12-15 4:18 ` Fam Zheng
2015-12-15 10:04 ` Vladimir Sementsov-Ogievskiy
2015-12-15 16:40 ` John Snow
2015-12-21 12:20 ` Vladimir Sementsov-Ogievskiy
2015-12-15 9:58 ` Kevin Wolf
2015-12-15 14:03 ` Max Reitz
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=20151215043447.GC19034@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=den@openvz.org \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.