From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38429) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eKniv-0003si-VD for qemu-devel@nongnu.org; Fri, 01 Dec 2017 11:00:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eKniF-0006B7-9Z for qemu-devel@nongnu.org; Fri, 01 Dec 2017 10:59:33 -0500 References: <20171012185916.22776-1-eblake@redhat.com> <20171012185916.22776-20-eblake@redhat.com> <1e4fe094-88bf-f2b8-1453-9c30f98e78e5@virtuozzo.com> From: Eric Blake Message-ID: <8c067b3d-5ec2-73fa-bc5b-5620ad6f2210@redhat.com> Date: Thu, 30 Nov 2017 17:31:27 -0600 MIME-Version: 1.0 In-Reply-To: <1e4fe094-88bf-f2b8-1453-9c30f98e78e5@virtuozzo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v4 19/20] vvfat: Switch to .bdrv_co_block_status() List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Vladimir Sementsov-Ogievskiy , qemu-devel@nongnu.org Cc: kwolf@redhat.com, jsnow@redhat.com, famz@redhat.com, qemu-block@nongnu.org, Max Reitz On 11/30/2017 06:25 AM, Vladimir Sementsov-Ogievskiy wrote: > 12.10.2017 21:59, Eric Blake wrote: >> We are gradually moving away from sector-based interfaces, towards >> byte-based.=C2=A0 Update the vvfat driver accordingly.=C2=A0 Note that= we >> can rely on the block driver having already clamped limits to our >> block size, and simplify accordingly. >> >> Signed-off-by: Eric Blake >=20 > Reviewed-by: Vladimir Sementsov-Ogievskiy >=20 >> vvfat_co_get_block_status(BlockDriverState *bs, >> -=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 int64_t sector_num, int nb= _sectors, int *n, BlockDriverState=20 >> **file) >> +static int coroutine_fn vvfat_co_block_status(BlockDriverState *bs, >> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 bool want_zero, int64= _t=20 >> offset, >> +=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 int64_t bytes, int64_= t *n, >=20 > may be rename to *pnum ? I don't see it making a difference; it would match the callback=20 definition more closely, but the code is short enough that it's not that=20 confusing with keeping the naming as-is. --=20 Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3266 Virtualization: qemu.org | libvirt.org