From: Song Liu <songliubraving@fb.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Kernel Team <Kernel-team@fb.com>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"Masami Hiramatsu" <mhiramat@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Jiri Olsa" <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexey Budankov <alexey.budankov@linux.intel.com>
Subject: Re: [RFC] perf/core: allow ftrace for functions in kernel/event/core.c
Date: Mon, 15 Jun 2020 18:27:48 +0000 [thread overview]
Message-ID: <CC73BE8A-E727-46BC-A28C-4964B5A71678@fb.com> (raw)
In-Reply-To: <20200605180222.6cc3b34c@oasis.local.home>
Hi Steven,
> On Jun 5, 2020, at 3:02 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Fri, 5 Jun 2020 21:58:48 +0000
> Song Liu <songliubraving@fb.com> wrote:
>
>>
>> How does this work in your tests?
>
> I started it, but got distracted by other work. It did not crash with
> the little testing I did do. I wanted to also look at my patch that
> adds tracing to the ftrace directory too.
>
> I'll try to remember to address this some more next week. Feel free to
> ping me again then.
Have you got chance to run these tests?
Thanks,
Song
next prev parent reply other threads:[~2020-06-15 18:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200526212826.4097888-1-songliubraving@fb.com>
2020-05-26 21:39 ` [RFC] perf/core: allow ftrace for functions in kernel/event/core.c Peter Zijlstra
2020-05-26 21:46 ` Song Liu
2020-05-26 21:54 ` Peter Zijlstra
2020-05-26 22:04 ` Steven Rostedt
2020-05-26 22:05 ` Steven Rostedt
2020-05-26 22:09 ` Song Liu
2020-06-05 21:58 ` Song Liu
2020-06-05 22:02 ` Steven Rostedt
2020-06-15 18:27 ` Song Liu [this message]
2021-09-24 17:15 ` Song Liu
2020-05-26 22:08 ` Song Liu
2020-05-27 5:40 ` Masami Hiramatsu
2020-05-27 18:40 ` Song Liu
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=CC73BE8A-E727-46BC-A28C-4964B5A71678@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=acme@redhat.com \
--cc=alexey.budankov@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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).