lkml.org 
[lkml]   [2004]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: boot_cpu_data vs current_cpu_data in voluntary-preempt-2.6.9-rc2-mm1-S1

On Sun, 19 Sep 2004, Dominik Brodowski wrote:

> Your voluntary-preempt-2.6.9-rc2-mm1-S1 patch contains this change
>
> @@ -34,7 +34,7 @@ inline void __const_udelay(unsigned long
> xloops *= 4;
> __asm__("mull %0"
> :"=d" (xloops), "=&a" (d0)
> - :"1" (xloops),"0" (current_cpu_data.loops_per_jiffy *
> (HZ/4)));
> + :"1" (xloops),"0" (boot_cpu_data.loops_per_jiffy * (HZ/4)));

this comes from the BKL patch - this is done to avoid false positives in
the smp_processor_id() debugger.

Ingo
-
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-03-22 14:06    [W:0.022 / U:0.672 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site