From: Pedro Alves <palves@redhat.com>
To: Markus Metzger <markus.t.metzger@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 00/17] record btrace: non-stop and ASNS
Date: Fri, 11 Sep 2015 07:56:00 -0000 [thread overview]
Message-ID: <55F28939.5070305@redhat.com> (raw)
In-Reply-To: <1441954298-25298-1-git-send-email-markus.t.metzger@intel.com>
On 09/11/2015 07:51 AM, Markus Metzger wrote:
> Changes to v1:
> - reworked non-stop test
> - changed the error string when trying to store registers while replaying
> - fixed all-stop/non-stop confusion in comments
>
> This patch series adds support for non-stop mode to the record btrace target
> and prepares for all-stop on top of non-stop (ASNS).
>
> It adds a new scheduler-locking mode "reverse" for the current record btrace
> behaviour of scheduler-locking during reverse/replay execution.
>
> I tested this with the current all-stop and with Pedro's ASNS (by reverting
> his disable patch).
>
> The patch series can also be found on branch users/mmetzger/btrace-non-stop.
Thanks Markus. The core changes are OK. The btrace changes all LGTM too.
Excellent work.
--
Pedro Alves
next prev parent reply other threads:[~2015-09-11 7:56 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 6:52 Markus Metzger
2015-09-11 6:51 ` [PATCH v2 05/17] btrace: split record_btrace_step_thread Markus Metzger
2015-09-11 6:51 ` [PATCH v2 06/17] btrace: move breakpoint checking into stepping functions Markus Metzger
2015-09-11 6:51 ` [PATCH v2 03/17] btrace: improve stepping debugging Markus Metzger
2015-09-11 6:51 ` [PATCH v2 11/17] btrace: async Markus Metzger
2015-09-11 6:51 ` [PATCH v2 07/17] btrace: add missing NO_HISTORY Markus Metzger
2015-09-11 6:51 ` [PATCH v2 01/17] btrace: fix non-stop check in to_wait Markus Metzger
2015-09-11 6:51 ` [PATCH v2 08/17] btrace: lock-step Markus Metzger
2015-09-11 6:51 ` [PATCH v2 12/17] infrun: switch to NO_HISTORY thread Markus Metzger
2015-09-11 6:51 ` [PATCH v2 04/17] btrace: extract the breakpoint check from record_btrace_step_thread Markus Metzger
2015-09-11 6:52 ` [PATCH v2 10/17] btrace: temporarily set inferior_ptid in record_btrace_start_replaying Markus Metzger
2015-09-11 6:52 ` [PATCH v2 09/17] btrace: resume all requested threads Markus Metzger
2015-09-11 6:52 ` [PATCH v2 15/17] btrace: allow full memory and register access for non-replaying threads Markus Metzger
2015-09-11 6:52 ` [PATCH v2 17/17] infrun: scheduler-locking reverse Markus Metzger
2015-09-11 7:01 ` Eli Zaretskii
2015-09-11 8:55 ` Pedro Alves
2015-09-11 9:02 ` Eli Zaretskii
2015-09-16 12:28 ` Metzger, Markus T
2015-09-16 12:54 ` Pedro Alves
2015-09-16 13:32 ` Pedro Alves
2015-09-16 13:56 ` Metzger, Markus T
2015-09-16 14:25 ` Pedro Alves
2015-09-11 6:52 ` [PATCH v2 16/17] target: add to_record_stop_replaying target method Markus Metzger
2015-09-11 6:52 ` [PATCH v2 14/17] target, record: add PTID argument to to_record_is_replaying Markus Metzger
2015-09-11 6:52 ` [PATCH v2 02/17] btrace: support to_stop Markus Metzger
2015-09-11 6:52 ` [PATCH v2 13/17] btrace: non-stop Markus Metzger
2015-09-11 6:58 ` Eli Zaretskii
2015-09-11 7:56 ` Pedro Alves [this message]
2015-09-11 8:02 ` [PATCH v2 00/17] record btrace: non-stop and ASNS Metzger, Markus T
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=55F28939.5070305@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.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