From: Steven Rostedt <rostedt@goodmis.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
bpf@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>,
Hari Bathini <hbathini@linux.ibm.com>,
Jordan Niethe <jniethe5@gmail.com>, Jiri Olsa <jolsa@redhat.com>,
linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
Yauheni Kaliuta <yauheni.kaliuta@redhat.com>
Subject: Re: [RFC PATCH 2/3] powerpc/ftrace: Override ftrace_location_lookup() for MPROFILE_KERNEL
Date: Thu, 10 Feb 2022 12:01:52 -0500 [thread overview]
Message-ID: <20220210120152.00d24b64@gandalf.local.home> (raw)
In-Reply-To: <1644508338.5ucomwqtts.naveen@linux.ibm.com>
On Thu, 10 Feb 2022 16:40:28 +0000
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> The other option is to mark ftrace_cmp_recs() as a __weak function, but
> I have a vague recollection of you suggesting #ifdef rather than a
> __weak function in the past. I might be mis-remembering, so if you think
> making this a __weak function is better, I can do that.
No. If I wanted that I would have suggested it. I think this is the
prettiest of the ugly solutions out there ;-)
As I said, I can't think of a better solution, and we can go with this
until something else comes along.
-- Steve
WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Yauheni Kaliuta <yauheni.kaliuta@redhat.com>,
Jordan Niethe <jniethe5@gmail.com>,
linuxppc-dev@lists.ozlabs.org, bpf@vger.kernel.org,
Jiri Olsa <jolsa@redhat.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Hari Bathini <hbathini@linux.ibm.com>
Subject: Re: [RFC PATCH 2/3] powerpc/ftrace: Override ftrace_location_lookup() for MPROFILE_KERNEL
Date: Thu, 10 Feb 2022 12:01:52 -0500 [thread overview]
Message-ID: <20220210120152.00d24b64@gandalf.local.home> (raw)
In-Reply-To: <1644508338.5ucomwqtts.naveen@linux.ibm.com>
On Thu, 10 Feb 2022 16:40:28 +0000
"Naveen N. Rao" <naveen.n.rao@linux.vnet.ibm.com> wrote:
> The other option is to mark ftrace_cmp_recs() as a __weak function, but
> I have a vague recollection of you suggesting #ifdef rather than a
> __weak function in the past. I might be mis-remembering, so if you think
> making this a __weak function is better, I can do that.
No. If I wanted that I would have suggested it. I think this is the
prettiest of the ugly solutions out there ;-)
As I said, I can't think of a better solution, and we can go with this
until something else comes along.
-- Steve
next prev parent reply other threads:[~2022-02-10 17:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-07 7:07 [RFC PATCH 0/3] powerpc64/bpf: Add support for BPF Trampolines Naveen N. Rao
2022-02-07 7:07 ` Naveen N. Rao
2022-02-07 7:07 ` [RFC PATCH 1/3] ftrace: Add ftrace_location_lookup() to lookup address of ftrace location Naveen N. Rao
2022-02-07 7:07 ` Naveen N. Rao
2022-02-07 7:07 ` [RFC PATCH 2/3] powerpc/ftrace: Override ftrace_location_lookup() for MPROFILE_KERNEL Naveen N. Rao
2022-02-07 7:07 ` Naveen N. Rao
2022-02-07 15:24 ` Steven Rostedt
2022-02-07 15:24 ` Steven Rostedt
2022-02-09 17:50 ` Naveen N. Rao
2022-02-09 17:50 ` Naveen N. Rao
2022-02-09 21:10 ` Steven Rostedt
2022-02-09 21:10 ` Steven Rostedt
2022-02-10 13:58 ` Naveen N. Rao
2022-02-10 13:58 ` Naveen N. Rao
2022-02-10 14:59 ` Steven Rostedt
2022-02-10 14:59 ` Steven Rostedt
2022-02-10 16:40 ` Naveen N. Rao
2022-02-10 16:40 ` Naveen N. Rao
2022-02-10 17:01 ` Steven Rostedt [this message]
2022-02-10 17:01 ` Steven Rostedt
2022-02-11 11:36 ` Naveen N. Rao
2022-02-11 11:36 ` Naveen N. Rao
2022-02-07 7:07 ` [RFC PATCH 3/3] powerpc64/bpf: Add support for bpf trampolines Naveen N. Rao
2022-02-07 7:07 ` Naveen N. Rao
2022-02-11 14:40 ` [RFC PATCH 0/3] powerpc64/bpf: Add support for BPF Trampolines Christophe Leroy
2022-02-11 14:40 ` Christophe Leroy
2022-02-14 10:47 ` Naveen N. Rao
2022-02-14 10:47 ` Naveen N. Rao
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=20220210120152.00d24b64@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=alexei.starovoitov@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=hbathini@linux.ibm.com \
--cc=jniethe5@gmail.com \
--cc=jolsa@redhat.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=yauheni.kaliuta@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.