From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH v2 0/4] scripts/qemu-gdb: Split into modules
Date: Wed, 2 Sep 2015 15:05:25 +0100 [thread overview]
Message-ID: <20150902140525.GG1924@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <1439574392-4403-1-git-send-email-peter.maydell@linaro.org>
On Fri, Aug 14, 2015 at 06:46:28PM +0100, Peter Maydell wrote:
> This patch series splits scripts/qemu-gdb into separate
> files for each command, to make it easier to add new
> commands in future without them all going into a single
> huge file.
>
> Patches 1 and 2 do that split, and have been on the list
> before (and reviewed by Stefan).
>
> Patch 3 makes the script tell gdb not to stop on SIGUSR1,
> since that's our SIGIPI and happens all the time.
>
> Patch 4 adds a brief comment explaining how to source the
> script. NB that I haven't attempted to make the script
> work with automatic-sourcing based on the executable
> being debugged. Somebody who uses the script that way
> can do that :-)
>
> I've dropped the script which added support for setting
> breakpoints on QEMU tracepoints for the moment (pending
> investigating static probe point support which might
> render it unnecessary). Mostly I'd like to get these
> into master so that future debug commands can go into
> the right place -- IIRC David Gilbert had a patchset
> which added another command.
>
> thanks
> -- PMM
>
> Peter Maydell (4):
> scripts/qemu-gdb: Split MtreeCommand into its own module
> scripts/qemu-gdb: Split CoroutineCommand into its own file
> scripts/qemu-gdb: Silently pass through SIGUSR1
> scripts/qemu-gdb: Add brief comment describing usage
>
> scripts/qemu-gdb.py | 146 ++++---------------------------------------
> scripts/qemugdb/__init__.py | 28 +++++++++
> scripts/qemugdb/coroutine.py | 91 +++++++++++++++++++++++++++
> scripts/qemugdb/mtree.py | 82 ++++++++++++++++++++++++
> 4 files changed, 212 insertions(+), 135 deletions(-)
> create mode 100644 scripts/qemugdb/__init__.py
> create mode 100644 scripts/qemugdb/coroutine.py
> create mode 100644 scripts/qemugdb/mtree.py
>
> --
> 1.9.1
>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
next prev parent reply other threads:[~2015-09-02 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 17:46 [Qemu-devel] [PATCH v2 0/4] scripts/qemu-gdb: Split into modules Peter Maydell
2015-08-14 17:46 ` [Qemu-devel] [PATCH v2 1/4] scripts/qemu-gdb: Split MtreeCommand into its own module Peter Maydell
2015-08-14 17:46 ` [Qemu-devel] [PATCH v2 2/4] scripts/qemu-gdb: Split CoroutineCommand into its own file Peter Maydell
2015-08-14 17:46 ` [Qemu-devel] [PATCH v2 3/4] scripts/qemu-gdb: Silently pass through SIGUSR1 Peter Maydell
2015-08-14 17:46 ` [Qemu-devel] [PATCH v2 4/4] scripts/qemu-gdb: Add brief comment describing usage Peter Maydell
2015-09-02 14:05 ` Stefan Hajnoczi [this message]
2015-09-11 17:01 ` [Qemu-devel] [PATCH v2 0/4] scripts/qemu-gdb: Split into modules Peter Maydell
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=20150902140525.GG1924@stefanha-thinkpad.redhat.com \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).