public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, benh@kernel.crashing.org
Subject: Re: [RFC/PATCH] Make printk work for really early debugging
Date: Thu, 18 May 2006 19:55:50 +1000	[thread overview]
Message-ID: <1147946150.7360.29.camel@localhost.localdomain> (raw)
In-Reply-To: <20060518023449.4e697b96.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 2040 bytes --]

On Thu, 2006-05-18 at 02:34 -0700, Andrew Morton wrote:
> Michael Ellerman <michael@ellerman.id.au> wrote:
> >
> > Currently printk is no use for early debugging because it refuses to actually
> >  print anything to the console unless cpu_online(smp_processor_id()) is true.
> > 
> >  The stated explanation is that console drivers may require per-cpu resources,
> >  or otherwise barf, because the system is not yet setup correctly. Fair enough.
> > 
> >  However some console drivers might be quite happy running early during boot,
> >  in fact we have one, and so it'd be nice if printk understood that.
> > 
> >  So I add a flag (which I would have called CON_BOOT, but that's taken) called
> >  CON_ANYTIME, which indicates that a console is happy to be called anytime,
> >  even if the cpu is not yet online.
> > 
> >  Tested on a Power 5 machine, with both a CON_ANYTIME driver and a bogus
> >  console driver that BUG()s if called while offline. No problems AFAICT.
> >  Built for i386 UP & SMP.
> 
> hm, OK.  But iirc is was just one silly ia64 console driver which had this
> problem.  It might be better to make the new behaviour be the default and mark
> the ia64 driver CON_NEEDS_CPU_ONLINE or something.
> 
> No?
> 
> Or go through and audit the drivers and sprinkle CON_ANYTIME in all the
> safe ones, maybe.

Quite possibly, I started from the assumption that we liked the current
behaviour. Inverting the logic, ie. CON_NEEDS_CPU_ONLINE, would be ok
with me, but it would be a much more intrusive change. All of a sudden
we'll be calling into all sorts of drivers that we didn't previously.

I'll trawl through the console drivers tomorrow and see if I can guess
what percentage look like they will/won't work, then we can decide which
way to flip it.

cheers

-- 
Michael Ellerman
IBM OzLabs

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]

  reply	other threads:[~2006-05-18  9:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18  9:14 [RFC/PATCH] Make printk work for really early debugging Michael Ellerman
2006-05-18  9:34 ` Andrew Morton
2006-05-18  9:55   ` Michael Ellerman [this message]
2006-05-18 10:07     ` Andrew Morton
2006-05-22  6:40       ` Michael Ellerman
2006-05-18 13:55 ` Andi Kleen
2006-05-18 15:41   ` Michael Ellerman
2006-05-18 16:00     ` Andi Kleen
2006-05-19  4:15       ` Michael Ellerman
2006-05-22  6:57   ` Michael Ellerman

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=1147946150.7360.29.camel@localhost.localdomain \
    --to=michael@ellerman.id.au \
    --cc=akpm@osdl.org \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.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