mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	linux-kernel@vger.kernel.org,
	Masami Hiramatsu <mhiramat@kernel.org>,
	"Jose E . Marchesi" <jose.marchesi@oracle.com>,
	Nick Desaulniers <ndesaulniers@google.com>,
	Sami Tolvanen <samitolvanen@google.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v3] tracepoint: Fix CFI failures with tp_sub_func
Date: Tue, 4 Apr 2023 16:22:41 -0400	[thread overview]
Message-ID: <20230404162232.1b2f4c2f@gandalf.local.home> (raw)
In-Reply-To: <ZCwDAnRHjNr9ZftR@FVFF77S0Q05N>

On Tue, 4 Apr 2023 11:59:26 +0100
Mark Rutland <mark.rutland@arm.com> wrote:

> Sorry to ping, but are you planning to pick this up, and/or did you want this
> resent with the Testing-by typo fixed?
> 
> I couldn't spot it in the tracing tree, and I'm not sure if it's still on your
> TODO list for review or has just been missed.

Actually, we may be going back to your original patches, as having a stub
function for every trace event will allow us to attach fprobes to them. And
we actually have a need to do that (connecting to tracepoints to get more
info than the trace event gives).

Masami is currently working on this.

-- Steve

  reply	other threads:[~2023-04-04 20:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 12:31 Mathieu Desnoyers
2023-03-24 12:33 ` Mathieu Desnoyers
2023-04-04 10:59   ` Mark Rutland
2023-04-04 20:22     ` Steven Rostedt [this message]
2023-04-08 14:03       ` Masami Hiramatsu
2023-04-11 17:14         ` 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=20230404162232.1b2f4c2f@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=jose.marchesi@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mhiramat@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=peterz@infradead.org \
    --cc=samitolvanen@google.com \
    /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

all inboxes | Powered by JetHome®