From: "Frank Ch. Eigler" <fche@redhat.com>
To: Anthony Eden <aeden@csail.mit.edu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
linux-trace-users@vger.kernel.org, kaslevs@vmware.com
Subject: Re: increase size of number of possible tracing events
Date: Mon, 1 Jul 2019 08:58:31 -0400 [thread overview]
Message-ID: <20190701125831.GA11858@redhat.com> (raw)
In-Reply-To: <CAHMsQjX4MH+nHB66s-95FGXpOz_O=XJwnQw6RJRaa_rchQMPeA@mail.gmail.com>
Hi -
> Using ptrace to do this turns out to be absurdly slow, as one might
> expect (I wrote a python script for lldb). If anyone would like to see
> the actual numbers let me know.
In the mean time, you can also try systemtap userspace probes. These
normally use kernel uprobes, but not the ftrace/perf-event mechanism,
so are not limited in number. A user can also opt to configure pure
userspace dyninst to instrument.
- FChE
prev parent reply other threads:[~2019-07-01 12:58 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
2019-06-30 14:31 ` Anthony Eden
2019-07-01 12:58 ` Frank Ch. Eigler [this message]
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=20190701125831.GA11858@redhat.com \
--to=fche@redhat.com \
--cc=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).