From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peterx@redhat.com, stefanha@redhat.com,
vsementsov@yandex-team.ru, den@virtuozzo.com,
andrey.drobyshev@virtuozzo.com
Subject: [PATCH v2 0/4] Fixes and improvements for scripts/qemugdb commands
Date: Tue, 2 Dec 2025 18:31:15 +0200 [thread overview]
Message-ID: <20251202163119.363969-1-andrey.drobyshev@virtuozzo.com> (raw)
v1 -> v2:
* Use pty module instead of script(1) for producing colored output;
* Patch coredump file in place instead of full copy;
* Save and restore original pt_regs values in a separate file;
* Wrap this logic in a separate class.
v1: https://lore.kernel.org/qemu-devel/20251125142105.448289-1-andrey.drobyshev@virtuozzo.com/
Andrey Drobyshev (4):
scripts/qemugdb: mtree: Fix OverflowError in mtree with 128-bit
addresses
scripts/qemugdb: timers: Fix KeyError in 'qemu timers' command
scripts/qemugdb: timers: Improve 'qemu timers' command readability
scripts/qemugdb: coroutine: Add option for obtaining detailed trace in
coredump
scripts/qemugdb/coroutine.py | 243 +++++++++++++++++++++++++++++++++--
scripts/qemugdb/mtree.py | 2 +-
scripts/qemugdb/timers.py | 54 ++++++--
3 files changed, 280 insertions(+), 19 deletions(-)
--
2.43.5
next reply other threads:[~2025-12-02 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 16:31 Andrey Drobyshev [this message]
2025-12-02 16:31 ` [PATCH v2 1/4] scripts/qemugdb: mtree: Fix OverflowError in mtree with 128-bit addresses Andrey Drobyshev
2025-12-02 16:31 ` [PATCH v2 2/4] scripts/qemugdb: timers: Fix KeyError in 'qemu timers' command Andrey Drobyshev
2025-12-02 16:31 ` [PATCH v2 3/4] scripts/qemugdb: timers: Improve 'qemu timers' command readability Andrey Drobyshev
2025-12-02 16:31 ` [PATCH v2 4/4] scripts/qemugdb: coroutine: Add option for obtaining detailed trace in coredump Andrey Drobyshev
2025-12-02 19:30 ` Stefan Hajnoczi
2025-12-03 9:39 ` Andrey Drobyshev
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=20251202163119.363969-1-andrey.drobyshev@virtuozzo.com \
--to=andrey.drobyshev@virtuozzo.com \
--cc=den@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@yandex-team.ru \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).