[lkml]   [2005]   [Nov]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Fastboot] Re: [PATCH 1/4] stack overflow safe kdump (i386) - safe_smp_processor_id
Andi Kleen <> writes:

> Fernando Luis Vazquez Cao <> writes:
>> To circumvent this problem I suggest implementing
>> "safe_smp_processor_id()" (it already exists on x86_64) for i386 and
>> IA64 and use it as a replacement to smp_processor_id in the reboot path
>> to the dump capture kernel. This is a possible implementation for i386.
> It's not fully safe, because a SMP kernel might run on a 32bit
> system without APIC. Then hard_smp_processor_id() would fault.
> (this cannot happen on x86-64)
> You probably need to check one of the globals set by apic.c
> when its disabled.

Right. An SMP kernel on a uniprocessor, without apics.

To my knowledge all SMP systems that linux supports have


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-11-29 05:19    [W:0.048 / U:3.076 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site