From: Michael Ellerman <michael@ellerman.id.au>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [RFC/PATCH] Make printk work for really early debugging
Date: Fri, 19 May 2006 01:41:26 +1000 [thread overview]
Message-ID: <1147966886.8469.4.camel@localhost.localdomain> (raw)
In-Reply-To: <p73y7wz30a1.fsf@bragg.suse.de>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
On Thu, 2006-05-18 at 15:55 +0200, Andi Kleen wrote:
> Michael Ellerman <michael@ellerman.id.au> writes:
>
> > 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.
>
> On x86-64 this is simply solved by setting the boot processor online very early.
Yeah, someone suggested that. Unfortunately it doesn't work, we actually
want to call printk before we even know which cpu we're on :D
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 --]
next prev parent reply other threads:[~2006-05-18 15:41 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
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 [this message]
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=1147966886.8469.4.camel@localhost.localdomain \
--to=michael@ellerman.id.au \
--cc=ak@suse.de \
--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