lkml.org 
[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
From
Date
Andi Kleen <ak@suse.de> writes:

> Fernando Luis Vazquez Cao <fernando@intellilink.co.jp> 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
apics.

Eric

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-11-29 05:19    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean