From: "Denis V. Lunev" <den@openvz.org>
Cc: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for 2.5 1/1] parallels: dirty BAT properly for continuous allocations
Date: Mon, 23 Nov 2015 11:31:39 +0300 [thread overview]
Message-ID: <5652CEEB.9010604@openvz.org> (raw)
In-Reply-To: <1447779778-26062-1-git-send-email-den@openvz.org>
On 11/17/2015 08:02 PM, Denis V. Lunev wrote:
> From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>
> This patch marks part of the BAT dirty properly. There is a possibility that
> multy-block allocation could have one block allocated on one BAT page and
> next block on the next page. The code without the patch could not save
> updated position to the file.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> block/parallels.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/parallels.c b/block/parallels.c
> index 4f79293..f689fde 100644
> --- a/block/parallels.c
> +++ b/block/parallels.c
> @@ -220,7 +220,7 @@ static int64_t allocate_clusters(BlockDriverState *bs, int64_t sector_num,
> s->bat_bitmap[idx + i] = cpu_to_le32(s->data_end / s->off_multiplier);
> s->data_end += s->tracks;
> bitmap_set(s->bat_dirty_bmap,
> - bat_entry_off(idx) / s->bat_dirty_block, 1);
> + bat_entry_off(idx + i) / s->bat_dirty_block, 1);
> }
>
> return bat2sect(s, idx) + sector_num % s->tracks;
Stefan,
how should we proceed with this? Should I send this as
a pull request or you could take this yourself?
Den
next prev parent reply other threads:[~2015-11-23 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 17:02 [Qemu-devel] [PATCH for 2.5 1/1] parallels: dirty BAT properly for continuous allocations Denis V. Lunev
2015-11-23 8:31 ` Denis V. Lunev [this message]
2015-11-23 10:24 ` Stefan Hajnoczi
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=5652CEEB.9010604@openvz.org \
--to=den@openvz.org \
--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.