qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>, Peter Lieven <pl@kamp.de>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] [PATCH 07/11] block/raw: add bdrv_co_write_zeroes
Date: Fri, 19 Jul 2013 16:38:48 +0800	[thread overview]
Message-ID: <1374223132-29107-8-git-send-email-stefanha@redhat.com> (raw)
In-Reply-To: <1374223132-29107-1-git-send-email-stefanha@redhat.com>

From: Peter Lieven <pl@kamp.de>

Signed-off-by: Peter Lieven <pl@kamp.de>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
---
 block/raw.c | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/block/raw.c b/block/raw.c
index ce10422..8c81de9 100644
--- a/block/raw.c
+++ b/block/raw.c
@@ -42,6 +42,13 @@ static int coroutine_fn raw_co_is_allocated(BlockDriverState *bs,
     return bdrv_co_is_allocated(bs->file, sector_num, nb_sectors, pnum);
 }
 
+static int coroutine_fn raw_co_write_zeroes(BlockDriverState *bs,
+                                            int64_t sector_num,
+                                            int nb_sectors)
+{
+    return bdrv_co_write_zeroes(bs->file, sector_num, nb_sectors);
+}
+
 static int64_t raw_getlength(BlockDriverState *bs)
 {
     return bdrv_getlength(bs->file);
@@ -128,6 +135,7 @@ static BlockDriver bdrv_raw = {
     .bdrv_co_readv          = raw_co_readv,
     .bdrv_co_writev         = raw_co_writev,
     .bdrv_co_is_allocated   = raw_co_is_allocated,
+    .bdrv_co_write_zeroes   = raw_co_write_zeroes,
     .bdrv_co_discard        = raw_co_discard,
 
     .bdrv_probe         = raw_probe,
-- 
1.8.1.4

  parent reply	other threads:[~2013-07-19  8:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-19  8:38 [Qemu-devel] [PULL for-1.6 00/11] Block patches Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 01/11] gluster: Use pkg-config to configure GlusterFS block driver Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 02/11] gluster: Add discard support for " Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 03/11] dataplane: sync virtio.c and vring.c virtqueue state Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 04/11] QEMUBH: make AioContext's bh re-entrant Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 05/11] block: fix vvfat error path for enable_write_target Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 06/11] block: add bdrv_write_zeroes() Stefan Hajnoczi
2013-07-19  8:38 ` Stefan Hajnoczi [this message]
2013-07-19  8:38 ` [Qemu-devel] [PATCH 08/11] block-migration: efficiently encode zero blocks Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 09/11] cpus: Let vm_stop[_force_state]() always flush block devices Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 10/11] block: fix bdrv_read_unthrottled() Stefan Hajnoczi
2013-07-19  8:38 ` [Qemu-devel] [PATCH 11/11] block/raw: add .bdrv_get_info 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=1374223132-29107-8-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=pl@kamp.de \
    --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).