[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [RFC PATCH 02/16] block: Set dirty before doing write
From: |
John Snow |
Subject: |
Re: [Qemu-devel] [RFC PATCH 02/16] block: Set dirty before doing write |
Date: |
Mon, 8 Feb 2016 19:11:04 -0500 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 |
On 01/26/2016 05:38 AM, Fam Zheng wrote:
> So that driver can write the dirty bits into persistent dirty bitmaps in
> the write callback.
>
> Signed-off-by: Fam Zheng <address@hidden>
> ---
> block/io.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/block/io.c b/block/io.c
> index 343ff1f..b964e7e 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -1164,6 +1164,8 @@ static int coroutine_fn
> bdrv_aligned_pwritev(BlockDriverState *bs,
> }
> }
>
> + bdrv_set_dirty(bs, sector_num, nb_sectors);
> +
> if (ret < 0) {
> /* Do nothing, write notifier decided to fail this request */
> } else if (flags & BDRV_REQ_ZERO_WRITE) {
> @@ -1179,8 +1181,6 @@ static int coroutine_fn
> bdrv_aligned_pwritev(BlockDriverState *bs,
> ret = bdrv_co_flush(bs);
> }
>
> - bdrv_set_dirty(bs, sector_num, nb_sectors);
> -
> if (bs->wr_highest_offset < offset + bytes) {
> bs->wr_highest_offset = offset + bytes;
> }
>
Might want a comment here acknowledging the write gets errantly set on
write failure, but that for $reasons it needs to be above anyway -- so
someone doesn't helpfully try to move it back below.
Reviewed-by: John Snow <address@hidden>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Qemu-devel] [RFC PATCH 02/16] block: Set dirty before doing write,
John Snow <=