Linux Trace Kernel
 help / color / mirror / Atom feed
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 10:12:33 -0500	[thread overview]
Message-ID: <20241119101233.19005043@gandalf.local.home> (raw)
In-Reply-To: <CAH5fLgjBpz7bPvanupPSsJx3fjLAa7g7nMjLgSxjEde_KDGV2w@mail.gmail.com>

On Tue, 19 Nov 2024 09:36:38 +0100
Alice Ryhl <aliceryhl@google.com> wrote:

> I've only really used the sample in this series as a build test. The
> bulk of my testing has occurred by using this tracepoint support in
> Rust Binder where I have 30 different tracepoints and I've been able
> to verify that I can enable them and so on there.

Could you modify the sample code to have a tracepoint that I could enable.
I don't use the Rust Binder code so I can't test it. I use the trace_event
sample code for selftests, and it would also be a good idea to add the rust
trace event sample to the self tests as well.

Would you be able to create some simple code to do that? If you add
something in the rust sample code, I'll add it to the ftrace selftests.

Thanks,

-- Steve

  reply	other threads:[~2024-11-19 15:12 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 [this message]
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

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=20241119101233.19005043@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