qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, pbonzini@redhat.com, stefanha@redhat.com,
	qemu-block@nongnu.org
Subject: [Qemu-devel] [PATCH v3 02/12] nbd: Mark fd handlers client type as "external"
Date: Fri, 16 Oct 2015 18:12:13 +0800	[thread overview]
Message-ID: <1444990343-25109-3-git-send-email-famz@redhat.com> (raw)
In-Reply-To: <1444990343-25109-1-git-send-email-famz@redhat.com>

So we could distinguish it from internal used fds, thus avoid handling
unwanted events in nested aio polls.

Signed-off-by: Fam Zheng <famz@redhat.com>
---
 nbd.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/nbd.c b/nbd.c
index 32a1f66..b599e62 100644
--- a/nbd.c
+++ b/nbd.c
@@ -1446,7 +1446,7 @@ static void nbd_set_handlers(NBDClient *client)
 {
     if (client->exp && client->exp->ctx) {
         aio_set_fd_handler(client->exp->ctx, client->sock,
-                           false,
+                           true,
                            client->can_read ? nbd_read : NULL,
                            client->send_coroutine ? nbd_restart_write : NULL,
                            client);
@@ -1457,7 +1457,7 @@ static void nbd_unset_handlers(NBDClient *client)
 {
     if (client->exp && client->exp->ctx) {
         aio_set_fd_handler(client->exp->ctx, client->sock,
-                           false, NULL, NULL, NULL);
+                           true, NULL, NULL, NULL);
     }
 }
 
-- 
2.4.3

  parent reply	other threads:[~2015-10-16 10:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 10:12 [Qemu-devel] [PATCH v3 00/12] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 01/12] aio: Add "is_external" flag for event handlers Fam Zheng
2015-10-16 10:12 ` Fam Zheng [this message]
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 03/12] dataplane: Mark host notifiers' client type as "external" Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 04/12] aio: introduce aio_{disable, enable}_external Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 05/12] block: Introduce "drained begin/end" API Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 06/12] block: Add "drained begin/end" for transactional external snapshot Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 07/12] block: Add "drained begin/end" for transactional backup Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 08/12] block: Add "drained begin/end" for transactional blockdev-backup Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 09/12] block: Add "drained begin/end" for internal snapshot Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 10/12] block: Introduce BlockDriver.bdrv_drain callback Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 11/12] qed: Implement .bdrv_drain Fam Zheng
2015-10-16 10:12 ` [Qemu-devel] [PATCH v3 12/12] tests: Add test case for aio_disable_external Fam Zheng
2015-10-18 23:34 ` [Qemu-devel] [PATCH v3 00/12] block: Protect nested event loop with bdrv_drained_begin and bdrv_drained_end Fam Zheng

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=1444990343-25109-3-git-send-email-famz@redhat.com \
    --to=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).