From: Peter Xu <peterx@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Maxim Levitsky <mlevitsk@redhat.com>,
s_sourceforge@nedprod.com
Subject: Re: [PATCH 0/3] scripts/qemu-gdb: Make coroutine dumps to work with coredumps
Date: Thu, 12 Dec 2024 09:45:12 -0500 [thread overview]
Message-ID: <Z1r2-MPZ5sZZ8Qpf@x1n> (raw)
In-Reply-To: <Z1q65CpTxqRtMes_@redhat.com>
On Thu, Dec 12, 2024 at 11:28:52AM +0100, Kevin Wolf wrote:
> Am 11.12.2024 um 22:39 hat Peter Xu geschrieben:
> > On Wed, Dec 11, 2024 at 05:25:10PM -0300, Fabiano Rosas wrote:
> > > Peter Xu <peterx@redhat.com> writes:
> > >
> > > > Coroutines are used in many cases in block layers. It's also used in live
> > > > migration when on destination side, and it'll be handy to diagnose crashes
> > > > within a coroutine when we want to also know what other coroutines are
> > > > doing.
> > >
> > > Not sure if you've seen this message on the list:
> > >
> > > https://lore.kernel.org/r/f0ebccca-7a17-4da8-ac4a-71cf6d69abc3@mtasv.net
>
> Let me add Niall to this thread.
>
> > No I didn't. I only started looking at this because I got a bug a few days
> > ago that I need to look at the main coroutine where dest crashed, then
> > Stefan told me this script and also told me it only works with live session.
> > Ideally I'll need coredump debug-ability, then I figured it isn't too hard.
>
> I agree this is useful at least in the current state of things, and
> possibly in the future for QEMUs built without support for new gdb
> magic.
>
> > I saw that it didn't yet land gdb, and it's much more involved even if it
> > could be more generic. Not sure how the block developers think, personally
> > I prefer this much smaller change because it works on old systems, where I
> > can easily install gdb with package managers.
>
> I don't think this is a question of preferring one or the other! Your
> simple change works today with existing QEMU builds and has fewer
> requirements, but it's also more limited in functionality.
Ah, definitely..
I had no intention to mean that we should only merge one, but more of pure
thinking what I would like to use in the near future, even if the solution
landed at some point in both gdb and qemu.
I'll still need to look at the old systems that miss the generic solution,
so I'd still prefer using the scripts (which currently satisfies most of my
needs..).
>
> The gdb changes look really nice at the first sight, debugging
> coroutines as if they were threads is exactly what you want in most
> cases. So I'd love to see this. Of course, someone would have to first
> understand what needs to be done in detail and then implement the QEMU
> side of it once the gdb side is merged.
Yes, I wish that could happen some day, that by default gdb on top of QEMU
can dump coroutines.
Thanks,
--
Peter Xu
prev parent reply other threads:[~2024-12-12 14:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-11 20:17 [PATCH 0/3] scripts/qemu-gdb: Make coroutine dumps to work with coredumps Peter Xu
2024-12-11 20:17 ` [PATCH 1/3] scripts/qemu-gdb: Always do full stack dump for python errors Peter Xu
2024-12-11 20:17 ` [PATCH 2/3] scripts/qemu-gdb: Simplify fs_base fetching for coroutines Peter Xu
2024-12-11 20:17 ` [PATCH 3/3] scripts/qemu-gdb: Support coroutine dumps in coredumps Peter Xu
2024-12-11 20:21 ` Peter Xu
2024-12-11 20:25 ` [PATCH 0/3] scripts/qemu-gdb: Make coroutine dumps to work with coredumps Fabiano Rosas
2024-12-11 21:39 ` Peter Xu
2024-12-12 10:28 ` Kevin Wolf
2024-12-12 14:45 ` Peter Xu [this message]
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=Z1r2-MPZ5sZZ8Qpf@x1n \
--to=peterx@redhat.com \
--cc=farosas@suse.de \
--cc=kwolf@redhat.com \
--cc=mlevitsk@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=s_sourceforge@nedprod.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.