mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"Joel Fernandes (Google)" <joel.opensrc@gmail.com>,
	Abderrahmane Benbachir <abderrahmane.benbachir@polymtl.ca>
Subject: Re: [PATCH 0/4 v2] init, tracing: Add initcall trace events
Date: Fri, 6 Apr 2018 21:34:24 +0200	[thread overview]
Message-ID: <20180406193424.GM4082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180406151923.292cb09f@gandalf.local.home>

On Fri, Apr 06, 2018 at 03:19:23PM -0400, Steven Rostedt wrote:
> 
> Peter, Andrew,
> 
> This keeps initcall_debug printing printk()s, but adds the feature of
> those locations also being trace events. Are you OK if I add this?

Yeah, I don't see any real problems with it.

  reply	other threads:[~2018-04-06 19:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-06 19:08 [PATCH 0/4 v2] init, tracing: Steven Rostedt
2018-04-06 19:08 ` [PATCH 1/4 v2] init, tracing: Add initcall trace events Steven Rostedt
2018-04-06 19:08 ` [PATCH 2/4 v2] init, tracing: instrument security and console " Steven Rostedt
2018-04-06 19:08 ` [PATCH 3/4 v2] init, tracing: Have printk come through the trace events for initcall_debug Steven Rostedt
2018-04-09  5:32   ` [lkp-robot] [init, tracing] 2580d6b795: BUG:kernel_reboot-without-warning_in_boot_stage kernel test robot
2018-04-09 22:04     ` Steven Rostedt
2018-04-10  1:23       ` Ye Xiaolong
2018-04-10  2:41         ` Steven Rostedt
2018-04-10  3:14           ` Ye Xiaolong
2018-04-06 19:08 ` [PATCH 4/4 v2] init: Have initcall_debug still work without CONFIG_TRACEPOINTS Steven Rostedt
2018-04-07  8:18   ` kbuild test robot
2018-04-06 19:16 ` [PATCH 0/4 v2] init, tracing: Add initcall trace events Steven Rostedt
2018-04-06 19:19 ` Steven Rostedt
2018-04-06 19:34   ` Peter Zijlstra [this message]
2018-04-06 19:46     ` 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=20180406193424.GM4082@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=abderrahmane.benbachir@polymtl.ca \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=joel.opensrc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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®