From: Daniel Bristot de Oliveira <bristot@redhat.com>
To: Benjamin Steinke <benjamin.steinke@woks-audio.com>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>
Subject: Re: stopping ftrace on event
Date: Wed, 6 Jul 2022 13:31:00 +0200 [thread overview]
Message-ID: <c8aa45af-9a64-8318-71d6-91511afed8e6@redhat.com> (raw)
In-Reply-To: <4044532.36S9Iv5CRb@desktop>
On 7/6/22 10:50, Benjamin Steinke wrote:
> Hi all,
>
> I'm hunting sporadic high irq-handler latencies in a pcie driver by using
> ftrace. I'm currently using trace-cmd record but get way to large files due to
> the event being so infrequent.
>
> Is there a way to stop tracing or dump the current trace buffer when a specific
> event occurs?
https://www.kernel.org/doc/html/latest/trace/events.html#event-triggers ?
-- Daniel
> Thanks for your help,
> Benjamin
>
>
>
>
next parent reply other threads:[~2022-07-06 11:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4044532.36S9Iv5CRb@desktop>
2022-07-06 11:31 ` Daniel Bristot de Oliveira [this message]
2022-07-06 11:51 ` stopping ftrace on event Benjamin Steinke
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=c8aa45af-9a64-8318-71d6-91511afed8e6@redhat.com \
--to=bristot@redhat.com \
--cc=benjamin.steinke@woks-audio.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-trace-devel@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).