From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Max Reitz <mreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"qemu-block@nongnu.org" <qemu-block@nongnu.org>,
Denis Lunev <den@virtuozzo.com>
Subject: Re: [Qemu-devel] [PATCH 0/2] deal with BDRV_BLOCK_RAW
Date: Tue, 13 Aug 2019 14:46:50 +0000 [thread overview]
Message-ID: <48fa03d6-259d-9ded-dacb-a4975f8d24e4@virtuozzo.com> (raw)
In-Reply-To: <b0c32bfc-f4cf-0d46-beb8-ba4cf79b76c5@redhat.com>
13.08.2019 17:31, Max Reitz wrote:
> On 13.08.19 13:51, Kevin Wolf wrote:
>
> [...]
>
>> Hm... This is a mess. :-)
>
> Just out of curiosity: Why?
>
> Aren’t there only two things we really need from the block_status
> infrastructure?
>
> (1) Whether something is allocated in the given layer of the backing chain,
>
> (2) Whether we know that a given range reads as zeroes.
>
> Do we really need anything else?
>
qemu-img map?
1. We need to fix the bug somehow
2. We need to fix comment about different block-status flags, as it really
lacks information of what actually "DATA" means (together with *file).
And what finally means "allocated", can you define it precisely?
3. Fix nbd-server to be closer to NBD spec about block-status
I made several tries to imagine [1] and [2] but never succeeded..
--
Best regards,
Vladimir
next prev parent reply other threads:[~2019-08-13 14:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-12 18:11 [Qemu-devel] [PATCH 0/2] deal with BDRV_BLOCK_RAW Vladimir Sementsov-Ogievskiy
2019-08-12 18:11 ` [Qemu-devel] [PATCH 1/2] block/raw-format: switch to BDRV_BLOCK_DATA with BDRV_BLOCK_RECURSE Vladimir Sementsov-Ogievskiy
2019-08-13 11:04 ` Kevin Wolf
2019-08-13 11:28 ` Vladimir Sementsov-Ogievskiy
2019-08-13 12:01 ` Kevin Wolf
2019-08-13 13:21 ` [Qemu-devel] [Qemu-block] " Kevin Wolf
2019-08-13 14:46 ` Max Reitz
2019-08-13 14:43 ` [Qemu-devel] " Max Reitz
2019-08-13 14:56 ` Vladimir Sementsov-Ogievskiy
2019-08-13 15:03 ` Max Reitz
2019-08-13 15:22 ` Vladimir Sementsov-Ogievskiy
2019-08-13 16:07 ` Max Reitz
2019-08-13 15:41 ` Kevin Wolf
2019-08-13 15:54 ` Vladimir Sementsov-Ogievskiy
2019-08-13 16:08 ` Kevin Wolf
2019-08-13 16:32 ` Vladimir Sementsov-Ogievskiy
2019-08-14 6:27 ` Vladimir Sementsov-Ogievskiy
2019-08-13 16:21 ` Max Reitz
2019-08-12 18:11 ` [Qemu-devel] [PATCH 2/2] iotests: test mirroring qcow2 under raw format Vladimir Sementsov-Ogievskiy
2019-08-13 9:10 ` Kevin Wolf
2019-08-13 9:22 ` Vladimir Sementsov-Ogievskiy
2019-08-13 9:36 ` Kevin Wolf
2019-08-12 19:46 ` [Qemu-devel] [PATCH 0/2] deal with BDRV_BLOCK_RAW Max Reitz
2019-08-12 19:50 ` Max Reitz
2019-08-13 8:39 ` Vladimir Sementsov-Ogievskiy
2019-08-13 9:01 ` Vladimir Sementsov-Ogievskiy
2019-08-13 9:33 ` Vladimir Sementsov-Ogievskiy
2019-08-13 11:14 ` Vladimir Sementsov-Ogievskiy
2019-08-13 11:51 ` Kevin Wolf
2019-08-13 13:00 ` Vladimir Sementsov-Ogievskiy
2019-08-13 14:31 ` Max Reitz
2019-08-13 14:46 ` Vladimir Sementsov-Ogievskiy [this message]
2019-08-13 14:53 ` Max Reitz
2019-08-13 15:03 ` Kevin Wolf
2019-08-13 15:04 ` Max Reitz
2019-08-13 14:50 ` Eric Blake
2019-08-13 9:34 ` Kevin Wolf
2019-08-13 14:38 ` 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=48fa03d6-259d-9ded-dacb-a4975f8d24e4@virtuozzo.com \
--to=vsementsov@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).