All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@suse.de>
To: Peter Xu <peterx@redhat.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	peterx@redhat.com, Paolo Bonzini <pbonzini@redhat.com>,
	Maxim Levitsky <mlevitsk@redhat.com>
Subject: Re: [PATCH 0/3] scripts/qemu-gdb: Make coroutine dumps to work with coredumps
Date: Wed, 11 Dec 2024 17:25:10 -0300	[thread overview]
Message-ID: <87pllyezmh.fsf@suse.de> (raw)
In-Reply-To: <20241211201739.1380222-1-peterx@redhat.com>

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



  parent reply	other threads:[~2024-12-11 20:25 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 ` Fabiano Rosas [this message]
2024-12-11 21:39   ` [PATCH 0/3] scripts/qemu-gdb: Make coroutine dumps to work with coredumps Peter Xu
2024-12-12 10:28     ` Kevin Wolf
2024-12-12 14:45       ` Peter Xu

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=87pllyezmh.fsf@suse.de \
    --to=farosas@suse.de \
    --cc=kwolf@redhat.com \
    --cc=mlevitsk@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --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.