From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
patches@linaro.org
Subject: [Qemu-devel] [PATCH v2 3/4] scripts/qemu-gdb: Silently pass through SIGUSR1
Date: Fri, 14 Aug 2015 18:46:31 +0100 [thread overview]
Message-ID: <1439574392-4403-4-git-send-email-peter.maydell@linaro.org> (raw)
In-Reply-To: <1439574392-4403-1-git-send-email-peter.maydell@linaro.org>
SIGUSR1 is QEMU's IPI signal, and it gets sent a lot, so is
best silently passed through to the guest without stopping.
Make qemu-gdb.py do this bit of configuration for the user.
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
---
scripts/qemu-gdb.py | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/scripts/qemu-gdb.py b/scripts/qemu-gdb.py
index 1c94b2a..f98cd21 100644
--- a/scripts/qemu-gdb.py
+++ b/scripts/qemu-gdb.py
@@ -34,3 +34,7 @@ class QemuCommand(gdb.Command):
QemuCommand()
coroutine.CoroutineCommand()
mtree.MtreeCommand()
+
+# Default to silently passing through SIGUSR1, because QEMU sends it
+# to itself a lot.
+gdb.execute('handle SIGUSR1 pass noprint nostop')
--
1.9.1
next prev parent reply other threads:[~2015-08-14 17:51 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 ` Peter Maydell [this message]
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 ` [Qemu-devel] [PATCH v2 0/4] scripts/qemu-gdb: Split into modules Stefan Hajnoczi
2015-09-11 17:01 ` 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=1439574392-4403-4-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=armbru@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=patches@linaro.org \
--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 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).