[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] Weird iscsi/fd-event issue since recent merge of event

From: Paolo Bonzini
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
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1

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?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]