qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: kwolf@redhat.com, pbonzini@redhat.com, jcody@redhat.com,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v7 01/10] aio: Add "is_external" flag for event handlers
Date: Fri, 23 Oct 2015 15:58:52 +0100	[thread overview]
Message-ID: <20151023145852.GD5977@stefanha-x1.localdomain> (raw)
In-Reply-To: <1445569694-2765-2-git-send-email-famz@redhat.com>

On Fri, Oct 23, 2015 at 11:08:05AM +0800, Fam Zheng wrote:
> All callers pass in false, and the real external ones will switch to
> true in coming patches.
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>
> Reviewed-by: Jeff Cody <jcody@redhat.com>
> Reviewed-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  aio-posix.c                     |  6 ++++-
>  aio-win32.c                     |  5 ++++
>  async.c                         |  3 ++-
>  block/curl.c                    | 14 +++++-----
>  block/iscsi.c                   |  9 +++----
>  block/linux-aio.c               |  5 ++--
>  block/nbd-client.c              | 10 ++++---
>  block/nfs.c                     | 17 +++++-------
>  block/sheepdog.c                | 38 ++++++++++++++++++---------
>  block/ssh.c                     |  5 ++--
>  block/win32-aio.c               |  5 ++--
>  hw/block/dataplane/virtio-blk.c |  6 +++--
>  hw/scsi/virtio-scsi-dataplane.c | 24 +++++++++++------
>  include/block/aio.h             |  2 ++
>  iohandler.c                     |  3 ++-
>  nbd.c                           |  4 ++-
>  tests/test-aio.c                | 58 +++++++++++++++++++++++------------------
>  17 files changed, 130 insertions(+), 84 deletions(-)
> 
> diff --git a/aio-posix.c b/aio-posix.c
> index d477033..f0f9122 100644
> --- a/aio-posix.c
> +++ b/aio-posix.c
> @@ -25,6 +25,7 @@ struct AioHandler
>      IOHandler *io_write;
>      int deleted;
>      void *opaque;
> +    bool is_external;

Please explain why is_external is needed so this patch makes sense by
itself.

A doc comment explaining the semantics of this new flag would be best.
That way people modifying the code will know how to use it correctly.

  reply	other threads:[~2015-10-23 14:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23  3:08 [Qemu-devel] [PATCH v7 00/10] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 01/10] aio: Add "is_external" flag for event handlers Fam Zheng
2015-10-23 14:58   ` Stefan Hajnoczi [this message]
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 02/10] nbd: Mark fd handlers client type as "external" Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 03/10] dataplane: Mark host notifiers' " Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 04/10] aio: introduce aio_{disable, enable}_external Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 05/10] block: Introduce "drained begin/end" API Fam Zheng
2015-10-23 15:13   ` Stefan Hajnoczi
2015-10-26  1:35     ` Fam Zheng
2015-10-23 15:24   ` Stefan Hajnoczi
2015-10-26  1:42     ` Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 06/10] block: Add "drained begin/end" for transactional external snapshot Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 07/10] block: Add "drained begin/end" for transactional backup Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 08/10] block: Add "drained begin/end" for transactional blockdev-backup Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 09/10] block: Add "drained begin/end" for internal snapshot Fam Zheng
2015-10-23  3:08 ` [Qemu-devel] [PATCH v7 10/10] tests: Add test case for aio_disable_external Fam Zheng
2015-10-23 11:44 ` [Qemu-devel] [PATCH v7 00/10] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Kevin Wolf
2015-10-23 15:21 ` 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=20151023145852.GD5977@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).