From: Oleg Nesterov <oleg@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Namhyung Kim <namhyung@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ftrace: kill global_start_up
Date: Wed, 23 Jul 2014 21:51:00 +0200 [thread overview]
Message-ID: <20140723195100.GA30591@redhat.com> (raw)
In-Reply-To: <20140723145319.78722824@gandalf.local.home>
On 07/23, Steven Rostedt wrote:
>
> On Wed, 23 Jul 2014 20:29:11 +0200
> Oleg Nesterov <oleg@redhat.com> wrote:
>
> > Thanks for your report Steven, I updated my ~/people-i-hate file.
>
> Is that for me or Namhyung? Silly question, it has to be for Namhyung,
> as I'm sure I'm one of the first people already in that list.
Sure, you are already listed more than once.
> > probably even event_context_switch... I'll recheck and send the patch.
This one is used by probe_wakeup_sched_switch(), so we can't simply
remove it.
> > But what a user can do with other files? You obviously can't enable, say,
> > ftrace/bputs, if I understand correctly this is for trace_puts().
> >
>
> Yeah, as trace_printk() can turn into a trace_puts() we still want
> those to be read by trace-cmd. To do that, the formats for those files
> are exported.
Ah, indeed, thanks.
> See kernel/trace/trace_export.c and trace_entries.h
Yeeees, I already found them. And this wasn't easy ;)
Thanks,
Oleg.
prev parent reply other threads:[~2014-07-23 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-20 15:18 [PATCH] ftrace: kill global_start_up Oleg Nesterov
2014-07-21 13:47 ` Steven Rostedt
2014-07-21 13:50 ` Steven Rostedt
2014-07-23 18:29 ` Oleg Nesterov
2014-07-23 18:53 ` Steven Rostedt
2014-07-23 19:51 ` Oleg Nesterov [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=20140723195100.GA30591@redhat.com \
--to=oleg@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.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 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.