From: Yao Qi <qiyaoltc@gmail.com>
To: Antoine Tremblay <antoine.tremblay@ericsson.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH V2 5/5] Support tracepoints for ARM linux in GDBServer
Date: Wed, 16 Nov 2016 20:49:00 -0000 [thread overview]
Message-ID: <CAH=s-PPy+zTi1Q_jcjX3Qjo0q-fRKoEck=pMxPp1EJt2bJY3jA@mail.gmail.com> (raw)
In-Reply-To: <wwok1sycstbs.fsf@ericsson.com>
On Tue, Nov 15, 2016 at 2:36 PM, Antoine Tremblay
<antoine.tremblay@ericsson.com> wrote:
>>
>> This field is only useful to trap-based tracepoint. It signals that we
>> need to create a sub-class trap_based_tracepoint of struct tracepoint.
>>
>
> Currently struct tracepoint is a merged struct if you will of all the
> tracepoint types, fast, static, trap.
>
> Moving to a subclass for trap-based tracepoints, would require making a
> subclass for all the others too, static, fast. It would be quite
> inconsistent otherwise.
Yes, that is what we should do. Before we add something new, we need to
clean up the existing code if necessary.
>
> While I do not object to this change, I think it should be part of
> another patch series and that this change is orthogonal to the
> tracepoint support for arm.
>
> WDYT ?
>
It is not orthogonal to the tracepoint support. In contrary, we must
"sub-struct" or "sub-class" tracepoint first, and them add "kind"
field for trap-based tracepoint. Note that "struct tracepoint" is
used in IPA as well.
--
Yao (齐尧)
next prev parent reply other threads:[~2016-11-16 20:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 14:33 [PATCH V2 0/5] " Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 2/5] Enable tracing of pseudo-registers on ARM Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 4/5] Use FAST_TRACEPOINT_LABEL in range-stepping.exp Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 3/5] Improve tests to allow for targets that support trace but not ftrace Antoine Tremblay
2016-11-03 14:33 ` [PATCH V2 5/5] Support tracepoints for ARM linux in GDBServer Antoine Tremblay
2016-11-03 17:51 ` Eli Zaretskii
2016-11-03 18:12 ` Antoine Tremblay
2016-11-10 14:01 ` Yao Qi
2016-11-15 14:42 ` Antoine Tremblay
2016-11-16 20:49 ` Yao Qi [this message]
2016-11-03 14:33 ` [PATCH V2 1/5] Teach arm unwinders to terminate gracefully Antoine Tremblay
2016-11-07 9:25 ` [PATCH V2 0/5] Support tracepoints for ARM linux in GDBServer Yao Qi
[not found] ` <wwoka8dasqta.fsf@ericsson.com>
2016-11-08 15:34 ` Antoine Tremblay
2016-11-09 16:39 ` Yao Qi
2016-11-09 17:58 ` Antoine Tremblay
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='CAH=s-PPy+zTi1Q_jcjX3Qjo0q-fRKoEck=pMxPp1EJt2bJY3jA@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=antoine.tremblay@ericsson.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