From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] gdb command: qemu iohandlers
Date: Tue, 23 Jun 2015 16:02:32 +0100 [thread overview]
Message-ID: <20150623150232.GD2167@work-vm> (raw)
In-Reply-To: <CAFEAcA9qUxXisPdLf6H4njnvQccVFn5KbEr9Js4NAZ2w2eHJwg@mail.gmail.com>
* Peter Maydell (peter.maydell@linaro.org) wrote:
> On 23 June 2015 at 15:43, Dr. David Alan Gilbert (git)
> <dgilbert@redhat.com> wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > Add a gdb command to print the current set of IOHandlers and
> > if one of them is a thread yielding for data print the backtrace.
> >
> > Useful for debugging why an incoming migration has stalled, e.g.
>
> I'd rather we did the split of qemu-gdb.py into one subfile
> per command before adding new ones: see patches 1 and 2 in
> this series:
> https://lists.gnu.org/archive/html/qemu-devel/2015-05/msg02961.html
No problem - I'm happy to rework after that split goes in.
Note I'm using the bt_jmpbuf function which that patchset puts in coroutine.py;
maybe there would be a better way to share it.
Dave
>
> thanks
> -- PMM
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-06-23 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-23 14:43 [Qemu-devel] [PATCH] gdb command: qemu iohandlers Dr. David Alan Gilbert (git)
2015-06-23 14:54 ` Peter Maydell
2015-06-23 15:02 ` Dr. David Alan Gilbert [this message]
2015-06-24 15:19 ` Stefan Hajnoczi
2015-06-25 1:05 ` Fam Zheng
2015-06-25 9:08 ` Dr. David Alan Gilbert
2015-06-25 10:32 ` 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=20150623150232.GD2167@work-vm \
--to=dgilbert@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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.