From: Paolo Bonzini <pbonzini@redhat.com>
To: ronnie sahlberg <ronniesahlberg@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] Weird iscsi/fd-event issue since recent merge of event system changes
Date: Tue, 22 May 2012 11:15:06 +0200 [thread overview]
Message-ID: <4FBB591A.8020506@redhat.com> (raw)
In-Reply-To: <CAN05THQEhaeD8_-5mk_8Hm_-xGRtQorUK_HbUt-+Ozc-s+Px-w@mail.gmail.com>
Il 22/05/2012 11:07, ronnie sahlberg ha scritto:
> Below iscsi_aio_readv is printed when we enter this function.
> This function prepares a CDB and sets it up for queueing, but it does
> not actually write it to the socket.
> At the end of this function, we set up the events by calling
> iscsi_set_events() and we set it up for writeable.
>
> iscsi_process_write() is when we enter the fd-is-writeable callback.
>
> iscsi_aio_readv 1337676989.429822
> iscsi_set_events write_event?Y 1337676989.429834
> iscsi_process_write 1337676989.484424
> iscsi_set_events write_event?N 1337676989.484507
> iscsi_process_read 1337676989.484628
> iscsi_aio_read10_cb 1337676989.484647
> iscsi_set_events write_event?N 1337676989.484660
> iscsi_readv_writev_bh_cb 1337676989.484665
> iscsi_aio_readv 1337676989.484751
Can you add to the debugging a "strace -e select" (and also note down
what fd is used for the socket), and/or instrument
qemu_iohandler_{fill,poll} in qemu's iohandler.c?
Paolo
next prev parent reply other threads:[~2012-05-22 9:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 6:07 [Qemu-devel] Weird iscsi/fd-event issue since recent merge of event system changes ronnie sahlberg
2012-05-21 10:45 ` Kevin Wolf
2012-05-21 10:59 ` Paolo Bonzini
2012-05-21 11:00 ` ronnie sahlberg
2012-05-21 13:20 ` Stefan Hajnoczi
2012-05-22 9:07 ` ronnie sahlberg
2012-05-22 9:15 ` Paolo Bonzini [this message]
2012-05-22 9:15 ` ronnie sahlberg
2012-05-22 9:29 ` Paolo Bonzini
2012-05-22 9:48 ` ronnie sahlberg
2012-05-22 10:03 ` ronnie sahlberg
2012-05-22 16:31 ` Michael Tokarev
2012-05-25 6:53 ` ronnie sahlberg
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=4FBB591A.8020506@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.com \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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).