From: Pedro Alves <palves@redhat.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] Coalesce/aggregate (async) vCont packets/actions
Date: Wed, 17 Feb 2016 02:44:00 -0000 [thread overview]
Message-ID: <1455677091-13683-1-git-send-email-palves@redhat.com> (raw)
Since:
[PATCH 00/18] Remote all-stop on top of non-stop
https://www.sourceware.org/ml/gdb-patches/2015-10/msg00213.html
The remote target supports "maint set target-non-stop on". However
that's still not the default.
I thought I'd first try to aggregate vCont packets, because with
"maint set target-non-stop on", we go from:
- All-stop / "maint set target-non-stop off"
(gdb) c
Continuing.
(...)
Sending packet: $vCont;c#a8..
to:
- All-stop / "maint set target-non-stop on"
(gdb) c
Continuing.
(...)
Sending packet: $vCont;c:p2c45.2c45#7c...Packet received: OK
Sending packet: $vCont;c:p2c45.2c4f#ad...Packet received: OK
Sending packet: $vCont;c:p2c45.2c50#78...Packet received: OK
... one packet per thread ...
After the series, we'll get back:
(gdb) c
Continuing.
(...)
Sending packet: $vCont;c#a8...Packet received: OK
(Note the "OK", showing that that was indeed an async vCont resume.)
along with other "wildcard" vCont packets like, "vCont;s:p1.1;c".
Also pushed to the users/palves/vcont-coalesce-actions branch.
Pedro Alves (5):
gdb: Clean up remote.c:remote_resume
gdb: Free inferior->priv when inferior exits
gdb/doc: Clarify vCont packet description
gdbserver: Leave already-vCont-resumed threads as they were
gdb: Coalesce/aggregate (async) vCont packets/actions
gdb/doc/gdb.texinfo | 32 ++-
gdb/gdbserver/linux-low.c | 27 +++
gdb/gdbserver/server.c | 33 ++-
gdb/gdbserver/server.h | 4 +
gdb/inferior.c | 3 +
gdb/inferior.h | 6 +
gdb/infrun.c | 8 +
gdb/record-btrace.c | 11 +
gdb/record-full.c | 11 +
gdb/remote.c | 566 ++++++++++++++++++++++++++++++++++++++++------
gdb/target-delegates.c | 26 +++
gdb/target.c | 29 +++
gdb/target.h | 46 +++-
13 files changed, 705 insertions(+), 97 deletions(-)
--
1.9.3
next reply other threads:[~2016-02-17 2:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 2:44 Pedro Alves [this message]
2016-02-17 2:44 ` [PATCH 3/5] gdb/doc: Clarify vCont packet description Pedro Alves
2016-02-17 15:56 ` Eli Zaretskii
2016-02-17 2:44 ` [PATCH 2/5] gdb: Free inferior->priv when inferior exits Pedro Alves
2016-02-17 2:44 ` [PATCH 1/5] gdb: Clean up remote.c:remote_resume Pedro Alves
2016-02-17 11:45 ` Luis Machado
2016-02-17 12:32 ` Pedro Alves
2016-02-17 13:44 ` Luis Machado
2016-02-17 2:51 ` [PATCH 5/5] gdb: Coalesce/aggregate (async) vCont packets/actions Pedro Alves
2016-02-17 13:42 ` Luis Machado
2016-10-26 15:35 ` Pedro Alves
2016-02-17 2:51 ` [PATCH 4/5] gdbserver: Leave already-vCont-resumed threads as they were Pedro Alves
2016-02-17 11:46 ` Luis Machado
2016-02-17 12:32 ` Pedro Alves
2016-10-26 15:39 ` Pedro Alves
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=1455677091-13683-1-git-send-email-palves@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.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