From: Steven Rostedt <rostedt@goodmis.org>
To: Alice Ryhl <aliceryhl@google.com>
Cc: lkp@intel.com, boqun.feng@gmail.com, llvm@lists.linux.dev,
oe-kbuild-all@lists.linux.dev, ojeda@kernel.org,
linux-trace-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] jump_label: rust: pass a mut ptr to `static_key_count`
Date: Tue, 19 Nov 2024 11:52:21 -0500 [thread overview]
Message-ID: <20241119115221.72f14db3@gandalf.local.home> (raw)
In-Reply-To: <CAH5fLgj0xHFLH8CCno568KtiQd9uD2G8Gek60mRLF98FZn0H2A@mail.gmail.com>
On Tue, 19 Nov 2024 17:16:56 +0100
Alice Ryhl <aliceryhl@google.com> wrote:
> Mostly because of the merge window, though also because waiting would
> let me use things landing in 6.13 through other maintainer trees; this
> would let me have the sample declare a miscdevice. But what I can
> submit now is this: create a Rust file that exposes a function which
> just triggers a tracepoint, and then I can call that function from C
> somewhere in the ftrace selftests, and then afterwards the C code
> could assert that the tracepoint got triggered. Is there an existing
> ftrace test that I can look at to base my work on?
You can look at samples/trace_events/trace-events-sample.c which actually
creates a thread that runs periodically and triggers trace events.
And the test:
tools/testing/selftests/ftrace/test.d/dynevent/add_remove_tprobe_module.tc
Also the module:
samples/trace_printk/trace-printk.c
and the test:
tools/testing/selftests/ftrace/test.d/event/trace_printk.tc
-- Steve
prev parent reply other threads:[~2024-11-19 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202411181440.qEdcuyh6-lkp@intel.com>
2024-11-18 20:27 ` [PATCH RESEND] jump_label: rust: pass a mut ptr to `static_key_count` Alice Ryhl
2024-11-18 20:41 ` Miguel Ojeda
2024-11-18 23:28 ` Steven Rostedt
2024-11-19 8:36 ` Alice Ryhl
2024-11-19 15:12 ` Steven Rostedt
2024-11-19 15:31 ` Alice Ryhl
2024-11-19 15:53 ` Steven Rostedt
2024-11-19 16:16 ` Alice Ryhl
2024-11-19 16:52 ` Steven Rostedt [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=20241119115221.72f14db3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=aliceryhl@google.com \
--cc=boqun.feng@gmail.com \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ojeda@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