From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] gdb command: qemu aios, qemu aiohandlers
Date: Mon, 26 Oct 2015 09:27:20 +0800 [thread overview]
Message-ID: <20151026012720.GA28904@ad.usersys.redhat.com> (raw)
In-Reply-To: <CAJSP0QXREX4Uefqq3P-kgc9WPrT19p8gz9OHxetb24wN+vHkQw@mail.gmail.com>
On Fri, 10/23 11:09, Stefan Hajnoczi wrote:
> On Fri, Oct 23, 2015 at 10:32 AM, Fam Zheng <famz@redhat.com> wrote:
> > On Tue, 10/20 12:05, Dr. David Alan Gilbert (git) wrote:
> >> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >>
> >> Two new gdb commands are added:
> >>
> >> qemu iohandlers
> >>
> >> that dumps the list of waiting iohandlers, this is particularly
> >> useful for trying to figure out where an incoming migration is
> >> blocked. For 'fd_coroutine_enter' cases we dump a full backtrace.
> >>
> >> qemu aios
> >> that dumps the qemu_aio_context list.
> >
> > I'd assume "qemu aios" is a command to print the list of AioContext instances
> > rather than handlers in a particular context (qemu_aio_context). How about
> > "qemu handlers"?
>
> Seems fine to me but it would be useful to add an optional AioContext
> pointer argument.
>
> That way the command prints qemu_aio_context by default but can also
> be used to inspect arbitrary AioContexts.
>
That is a good idea.
Fam
next prev parent reply other threads:[~2015-10-26 1:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 11:05 [Qemu-devel] [PATCH] gdb command: qemu aios, qemu aiohandlers Dr. David Alan Gilbert (git)
2015-10-23 9:32 ` Fam Zheng
2015-10-23 10:09 ` Stefan Hajnoczi
2015-10-26 1:27 ` Fam Zheng [this message]
2015-10-26 3:14 ` Paolo Bonzini
2015-10-27 13:13 ` Dr. David Alan Gilbert
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=20151026012720.GA28904@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.