From: Anthony Eden <aeden@csail.mit.edu>
To: linux-trace-users@vger.kernel.org
Subject: increase size of number of possible tracing events
Date: Fri, 21 Jun 2019 18:14:54 -0400 [thread overview]
Message-ID: <CAHMsQjVYHY1N=X9emeYg34XxeUaMRdV--3NYFNdy111sD0-0gg@mail.gmail.com> (raw)
I am trying to develop a patch which increases the maximum number of
possible tracing events (i.e. TRACE_EVENT_TYPE_MAX). I naively tried
changing unsigned short trace_entry::type to unsigned int (that simply
broke tracing).
Short background: I am placing a UProbe tracepoint at the start of
every basic block for every DSO in a dynamically-linked program. I
recently hit the ceiling for the maximum number of tracepoints with
dnsmasq;
/usr/bin/dnsmasq: 12826 basic blocks
/usr/lib/libc.so.6: 60511 basic blocks
/lib64/ld-linux-x86-64.so.2: 6270 basic blocks
linux-vdso.so.1: 36 basic blocks
Writing to /sys/kernel/debug/tracing/uprobe_events returns -ENODEV. If
anyone could provide some guidance towards raising the limit, it would
be much appreciated.
Thanks,
-Anthony
next reply other threads:[~2019-06-21 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-21 22:14 Anthony Eden [this message]
2019-06-21 23:13 ` increase size of number of possible tracing events Steven Rostedt
2019-06-26 15:46 ` Steven Rostedt
2019-06-27 16:44 ` Anthony Eden
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='CAHMsQjVYHY1N=X9emeYg34XxeUaMRdV--3NYFNdy111sD0-0gg@mail.gmail.com' \
--to=aeden@csail.mit.edu \
--cc=linux-trace-users@vger.kernel.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).