qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: "Benoît Canet" <benoit.canet@irqsave.net>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 05/10] block/json: Add bdrv_co_get_block_status()
Date: Wed, 05 Mar 2014 21:10:03 +0100	[thread overview]
Message-ID: <5317849B.7030107@redhat.com> (raw)
In-Reply-To: <20140305161150.GG1709@irqsave.net>

On 05.03.2014 17:11, Benoît Canet wrote:
> The Monday 03 Mar 2014 à 16:28:48 (+0100), Max Reitz wrote :
>> Implement this function in the same way as raw_bsd does: Acknowledge
>> that this is a passthrough driver (always return BDRV_BLOCK_OFFSET_VALID
>> and BDRV_BLOCK_DATA and derive the offset directly from the sector
>> index) and add BDRV_BLOCK_RAW to the returned value.
>>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>>   block/json.c | 9 +++++++++
>>   1 file changed, 9 insertions(+)
>>
>> diff --git a/block/json.c b/block/json.c
>> index a2f4691..7392802 100644
>> --- a/block/json.c
>> +++ b/block/json.c
>> @@ -113,6 +113,14 @@ static coroutine_fn int json_co_write_zeroes(BlockDriverState *bs,
>>       return bdrv_co_write_zeroes(bs, sector_num, nb_sectors, flags);
>>   }
>>   
>> +static coroutine_fn int64_t json_co_get_block_status(BlockDriverState *bs,
>> +                                                     int64_t sector_num,
>> +                                                     int nb_sectors, int *pnum)
>> +{
>> +    return BDRV_BLOCK_RAW | BDRV_BLOCK_OFFSET_VALID | BDRV_BLOCK_DATA |
>> +           (sector_num << BDRV_SECTOR_BITS);
>> +}
> I don't understand what is the selling point of this method instead of calling
> bdrv_co_get_block_status on bs->file.
> Some information risk to be lost and it does look like magic.

This is the same what "raw" does. It just is more meaningful: This way, 
this function does not pretend to provide the blocks itself but instead 
tells the truth; that is, the blocks are provided by an underlying BDS 
(bs->file).

I wasn't really sure what to do myself. Generally, this driver is 
actually meant to pretend that it provides the blocks itself. On the 
other hand, I tried to imitate the behavior or "raw", since this is 
something I can hope to be approximately correct. Also, as I've said 
before, the value returned here is in fact at least technically correct.


Max

> Best regards
>
> Benoît
>
>> +
>>   static void json_invalidate_cache(BlockDriverState *bs)
>>   {
>>       return bdrv_invalidate_cache(bs->file);
>> @@ -159,6 +167,7 @@ static BlockDriver bdrv_json = {
>>       .bdrv_aio_discard           = json_aio_discard,
>>   
>>       .bdrv_co_write_zeroes       = json_co_write_zeroes,
>> +    .bdrv_co_get_block_status   = json_co_get_block_status,
>>   
>>       .bdrv_invalidate_cache      = json_invalidate_cache,
>>   
>> -- 
>> 1.9.0
>>
>>

  reply	other threads:[~2014-03-05 20:10 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-03 15:28 [Qemu-devel] [PATCH 00/10] block/json: Add JSON protocol driver Max Reitz
2014-03-03 15:28 ` [Qemu-devel] [PATCH 01/10] qdict: Add qdict_join() Max Reitz
2014-03-05 15:55   ` Benoît Canet
2014-03-05 16:01     ` Kevin Wolf
2014-03-05 16:06       ` Benoît Canet
2014-03-05 16:52   ` Eric Blake
2014-03-05 20:13     ` Max Reitz
2014-03-03 15:28 ` [Qemu-devel] [PATCH 02/10] block/json: Add JSON protocol driver Max Reitz
2014-03-05 16:04   ` Benoît Canet
2014-03-05 19:58     ` Max Reitz
2014-03-05 20:20       ` Benoît Canet
2014-03-05 20:21         ` Max Reitz
2014-03-05 21:18           ` Benoît Canet
2014-03-03 15:28 ` [Qemu-devel] [PATCH 03/10] block/json: Add functions for cache control Max Reitz
2014-03-05 16:07   ` Benoît Canet
2014-03-03 15:28 ` [Qemu-devel] [PATCH 04/10] block/json: Add functions for writing zeroes etc Max Reitz
2014-03-05 16:09   ` Benoît Canet
2014-03-05 20:03     ` Max Reitz
2014-03-03 15:28 ` [Qemu-devel] [PATCH 05/10] block/json: Add bdrv_co_get_block_status() Max Reitz
2014-03-05 16:11   ` Benoît Canet
2014-03-05 20:10     ` Max Reitz [this message]
2014-03-05 20:41       ` Benoît Canet
2014-03-05 20:44         ` Max Reitz
2014-03-05 23:22           ` Benoît Canet
2014-03-06 20:01             ` Max Reitz
2014-03-03 15:28 ` [Qemu-devel] [PATCH 06/10] block/json: Add ioctl etc Max Reitz
2014-03-05 16:14   ` Benoît Canet
2014-03-03 15:28 ` [Qemu-devel] [PATCH 07/10] block/json: Add bdrv_get_specific_info() Max Reitz
2014-03-05 16:15   ` Benoît Canet
2014-03-03 15:28 ` [Qemu-devel] [PATCH 08/10] block/raw_bsd: " Max Reitz
2014-03-05 16:16   ` Benoît Canet
2014-03-03 15:28 ` [Qemu-devel] [PATCH 09/10] block/qapi: Ignore filters on top for format name Max Reitz
2014-03-05 16:20   ` Benoît Canet
2014-03-05 20:11     ` Max Reitz
2014-03-03 15:28 ` [Qemu-devel] [PATCH 10/10] iotests: Add test for the JSON protocol Max Reitz
2014-03-05 17:27   ` Eric Blake
2014-03-05 20:15     ` Max Reitz
2014-03-05 20:27       ` Eric Blake
2014-03-05 16:26 ` [Qemu-devel] [PATCH 00/10] block/json: Add JSON protocol driver Eric Blake

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=5317849B.7030107@redhat.com \
    --to=mreitz@redhat.com \
    --cc=benoit.canet@irqsave.net \
    --cc=kwolf@redhat.com \
    --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).