All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 2/3][RFC] tracing: Add optional percpu buffers for trace_printk()
Date: Mon, 10 Oct 2011 09:17:05 -0400	[thread overview]
Message-ID: <1318252626.7904.85.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <1318251873.14400.30.camel@laptop>

On Mon, 2011-10-10 at 15:04 +0200, Peter Zijlstra wrote:
> On Mon, 2011-10-10 at 08:37 -0400, Steven Rostedt wrote:
> 
> > This will make debugging some of my embedded boards difficult (the ones
> > where I have no way to add kernel command lines). If there's a problem
> > at boot up, I will have to modify the kernel to get this to print.
> > 
> > For those that don't know the tracing code, it will just simply break.
> > 
> > Unless you want me to keep the kconfig option that enables it
> > permanently. Then I could do this.
> 
> There's a fairly easy fix for that, initialize it at boot, and free once
> userspace it up and running if no trace_printk() came by.

Hmm, I could do that. Of course this will add a check for a global
variable in all trace_printks. I could make it a read_mostly variable,
as it only gets updated once, or even encapsulate the entire check with
a static_switch() :)


> 
> > I also expect tglx to throw frozen sharks at me for "why doesn't
> > trace_printk() work anymore?!!!!"
> 
> I'm sure you'll get over that :-)

I've had too many, I'm not sure my head could take much more.

-- Steve



  reply	other threads:[~2011-10-10 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-08 17:02 [PATCH 0/3][RFC] trace_printk() using percpu buffers Steven Rostedt
2011-10-08 17:02 ` [PATCH 1/3][RFC] tracing: Do not allocate buffer for trace_marker Steven Rostedt
2011-10-08 17:02 ` [PATCH 2/3][RFC] tracing: Add optional percpu buffers for trace_printk() Steven Rostedt
2011-10-10 11:08   ` Peter Zijlstra
2011-10-10 12:37     ` Steven Rostedt
2011-10-10 13:04       ` Peter Zijlstra
2011-10-10 13:17         ` Steven Rostedt [this message]
2011-10-08 17:02 ` [PATCH 3/3][RFC] tracing: Add config to permanently have trace_printk() use percpu Steven Rostedt
2011-10-10 11:04 ` [PATCH 0/3][RFC] trace_printk() using percpu buffers Peter Zijlstra
2011-10-10 12:31   ` Steven Rostedt
2011-10-10 13:03     ` Peter Zijlstra
2011-10-10 13:06       ` 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=1318252626.7904.85.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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 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.