[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A014A9D.8000903@cn.fujitsu.com>
Date: Wed, 06 May 2009 16:30:21 +0800
From: Li Zefan <lizf@...fujitsu.com>
To: Yinghai Lu <yinghai@...nel.org>
CC: Ingo Molnar <mingo@...e.hu>,
Frederic Weisbecker <fweisbec@...il.com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Zhaolei <zhaolei@...fujitsu.com>,
Steven Rostedt <rostedt@...dmis.org>,
Vegard Nossum <vegard.nossum@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: printk %0*X is broken.
Ingo Molnar wrote:
> Cc:-ed more folks who modified lib/vsprintf.c recently.
>
> Ingo
>
> * Yinghai Lu <yinghai@...nel.org> wrote:
>
>> it seems someone broke
>>
>> printk( "%0*X\n", width, x);
>>
>> looks like 0 is dumped.
>>
>> YH
>>
>> [ 0.000000] MTRR variable ranges enabled:
>> [ 0.000000] 0 base 0 00000000 mask FF0 00000000 write-back
>> [ 0.000000] 1 base 10 00000000 mask FFF 80000000 write-back
>> [ 0.000000] 2 base 0 80000000 mask FFF 80000000 uncachable
>> [ 0.000000] 3 base 0 7F800000 mask FFF FF800000 uncachable
>>
2.6.30-rc4-tip, the output of my box:
high_width: 1
MTRR variable ranges enabled:
0 base 000000000 mask FC0000000 write-back
1 base 03C000000 mask FFC000000 uncachable
2 base 0D0000000 mask FF8000000 write-combining
Is it possible that high_width is negative in your output?
If high_width == -3, we can get exactly the same output with yours.
>>
>> code:
>> for (i = 0; i < num_var_ranges; ++i) {
>> if (mtrr_state.var_ranges[i].mask_lo & (1 << 11))
>> printk(KERN_DEBUG " %u base %0*X%05X000 mask %0*X%05X000 %s\n",
>> i,
>> high_width,
>> mtrr_state.var_ranges[i].base_hi,
>> mtrr_state.var_ranges[i].base_lo >> 12,
>> high_width,
>> mtrr_state.var_ranges[i].mask_hi,
>> mtrr_state.var_ranges[i].mask_lo >> 12,
>> mtrr_attrib_to_str(mtrr_state.var_ranges[i].base_lo & 0xff));
>> else
>> printk(KERN_DEBUG " %u disabled\n", i);
>> }
>>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists