On Thu, 2006-05-18 at 15:55 +0200, Andi Kleen wrote: > Michael Ellerman <[email protected]> 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. I had a closer look at this, and we could actually fudge it so that cpu_online() is true in our early boot code, even though we don't know what cpu we're on. But that kind of begs the question, what does "cpu_online(x)" actually mean? If it doesn't mean percpu data is allocated, what does it mean? 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:
signature.asc
Description: This is a digitally signed message part
- References:
- [RFC/PATCH] Make printk work for really early debugging
- From: Michael Ellerman <[email protected]>
- Re: [RFC/PATCH] Make printk work for really early debugging
- From: Andi Kleen <[email protected]>
- [RFC/PATCH] Make printk work for really early debugging
- Prev by Date: Re: [RFC/PATCH] Make printk work for really early debugging
- Next by Date: Re: __vmalloc with GFP_ATOMIC causes 'sleeping from invalid context'
- Previous by thread: Re: [RFC/PATCH] Make printk work for really early debugging
- Next by thread: [patch] fix magic sysrq on strange keyboards
- Index(es):
 |