From: Anthony Eden <aeden@csail.mit.edu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-users@vger.kernel.org, kaslevs@vmware.com
Subject: Re: increase size of number of possible tracing events
Date: Thu, 27 Jun 2019 12:44:48 -0400 [thread overview]
Message-ID: <CAHMsQjV_uuhf6XPB7xype--V87_d7KeEgeks-7Qfw-2GVzLSrw@mail.gmail.com> (raw)
In-Reply-To: <20190626114601.6510c943@gandalf.local.home>
> I'm not sure having over 65535 different events is a good idea. Perhaps
> we should create a different type of uprobe that can be reused, as I'm
> sure you are not making each of these events record different data.
> Basically make it similar to the function tracing event, which is a
> single event that records the function that it traces, and not
> thousands of different individual events.
>
> Would something like that be helpful for you? It still requires a
> kernel change, but that is still possible.
You're right; the events record no data. Optimizing for this use-case
sounds reasonable.
It would be very helpful. The basic-block traces produced by this
mechanism allow us to identify bugs introduced by transformations we
make on the binaries. Kernel changes are no problem.
-Anthony
next prev parent reply other threads:[~2019-06-27 16:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 22:14 increase size of number of possible tracing events Anthony Eden
2019-06-21 23:13 ` Steven Rostedt
2019-06-26 15:46 ` Steven Rostedt
2019-06-27 16:44 ` Anthony Eden [this message]
2019-06-30 14:31 ` Anthony Eden
2019-07-01 12:58 ` Frank Ch. Eigler
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=CAHMsQjV_uuhf6XPB7xype--V87_d7KeEgeks-7Qfw-2GVzLSrw@mail.gmail.com \
--to=aeden@csail.mit.edu \
--cc=kaslevs@vmware.com \
--cc=linux-trace-users@vger.kernel.org \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).