stepan at coresystems.de
Sat Jun 20 10:10:52 CEST 2009
On 20.06.2009 2:46 Uhr, Carl-Daniel Hailfinger wrote:
>>> A quick test abuild with #error inserted in the lockless function shows
>>> we indeed use it for every freaking x86 target.
>>> That explains the supermicro/h8dme intertwined printk messages Ward is
>> They're from ram init stage afaict ...
> If we need them instead of the generic variants, we should know a reason
> for such usage.
Yes, the reasons are
- no console "drivers" in the stage2/coreboot_ram style at this level
- no spinlocking because we have no ram that is available to and shared
by all cpus
>>> Besides that, do we know where static spinlock_t console_lock is placed?
>> In RAM
> So we'd get uninitialied data for any pre-RAM spinlock access? The v3
> global variable mechanism should solve this nicely. At least it was
> designed for that.
But was it designed for safe IPC (Inter Processor Communication ;-) ?
coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br.
Tel.: +49 761 7668825 • Fax: +49 761 7664613
Email: info at coresystems.de • http://www.coresystems.de/
Registergericht: Amtsgericht Freiburg • HRB 7656
Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the coreboot