linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Kay Sievers <kay@vrfy.org>, Steven Rostedt <rostedt@goodmis.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org,
	Greg Kroah-Hartmann <greg@kroah.com>,
	Lennart Poettering <lennart@poettering.net>
Subject: Re: cosmetic printk() issue with lockdep warning in arch/x86/kernel/alternative.c
Date: Fri, 29 Jun 2012 14:58:45 +0200	[thread overview]
Message-ID: <20120629125845.GA32730@gmail.com> (raw)
In-Reply-To: <1340795162.10063.28.camel@twins>


* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:

> On Wed, 2012-06-27 at 12:49 +0200, Kay Sievers wrote:
> > All we want is a reliable printk
> 
> We too, but we define reliable differently. I want printk() to 
> dump data ASAP so that it has better chance to get out of the 
> system and onto my console in case of a crash. I don't give a 
> rats arse about interleaved text, any text is better than no 
> text.

I actually *fixed* bugs in the past when I saw interleaved text 
printed from multiple CPUs, it told me how narrow and SMP 
dependent a particular race/crash was.

So even interleaving, although annoying most of the time, can be 
useful in some other places.

Thanks,

	Ingo

      parent reply	other threads:[~2012-06-29 12:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAPXgP124qFG=QdO4H7qsp1bhY4BOp-PJEz7-4v-Dhi13LW+GDQ@mail.gmail.com>
2012-06-27  6:09 ` cosmetic printk() issue with lockdep warning in arch/x86/kernel/alternative.c Ingo Molnar
2012-06-27 10:49   ` Kay Sievers
2012-06-27 11:06     ` Peter Zijlstra
2012-06-27 11:12       ` Kay Sievers
2012-06-27 14:44         ` Joe Perches
2012-06-29 12:58       ` Ingo Molnar [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=20120629125845.GA32730@gmail.com \
    --to=mingo@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.com \
    --cc=kay@vrfy.org \
    --cc=lennart@poettering.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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).