From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/3] Support range stepping on software single-step target
Date: Wed, 26 Oct 2016 17:34:00 -0000 [thread overview]
Message-ID: <wwokshrjrp3h.fsf@ericsson.com> (raw)
In-Reply-To: <CAH=s-PPxajDB1u88RE=g-CsX2h4cZp7uGFxQMEEveLYGAA07og@mail.gmail.com>
Yao Qi writes:
> On Mon, Oct 10, 2016 at 9:43 AM, Yao Qi <qiyaoltc@gmail.com> wrote:
>> Yao Qi <qiyaoltc@gmail.com> writes:
>>
>>> This patch series enables the range stepping on targets support software
>>> single-step, although arm-linux is the only target nowadays.
>>>
>>> Patch 1 is to remove single-step breakpoints for GDBserver internal
>>> events. Patch 2 teaches GDBserver to gen pending events from threads
>>> in random to avoid starvation. Patch 3 is to enable range stepping
>>> if software single-step is supported.
>>>
>>> Regression tested arm-linux and x86_64-linux.
>>
>> Ping.
>>
>
> Ping.
Hi, series LGTM.
I tested on my boards and non-stop-fair-events is now working fine,
thanks for this work!! Sorry for the review delay.
Regards,
Antoine
next prev parent reply other threads:[~2016-10-26 17:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 2:25 Yao Qi
2016-09-26 2:25 ` [PATCH 3/3] Enable range stepping if software single step is supported Yao Qi
2016-09-26 2:25 ` [PATCH 2/3] Get pending events in random Yao Qi
2016-09-26 2:47 ` [PATCH 1/3] Remove single-step breakpoint for GDBserver internal event Yao Qi
2016-10-26 17:45 ` Pedro Alves
2016-10-26 20:14 ` Yao Qi
2016-10-27 13:16 ` Pedro Alves
2016-10-27 14:14 ` Yao Qi
2016-10-27 14:14 ` Pedro Alves
2016-10-10 8:43 ` [PATCH 0/3] Support range stepping on software single-step target Yao Qi
2016-10-26 15:39 ` Yao Qi
2016-10-26 17:34 ` Antoine Tremblay [this message]
2016-10-27 15:07 ` Yao Qi
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=wwokshrjrp3h.fsf@ericsson.com \
--to=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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