Re: [Bug 11388] New: 2.6.27-rc3 warns about MTRR range; only 3 of 16gb of memory is usable

[Yinghai Lu]

On Thu, Aug 21, 2008 at 8:51 PM, Ingo Molnar <mingo@xxxxxxx> wrote:
>
> * Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:
>
>> On Thu, Aug 21, 2008 at 4:56 AM, Ingo Molnar <mingo@xxxxxxx> wrote:
>> >
>> > * Ingo Molnar <mingo@xxxxxxx> wrote:
>> >
>> >>
>> >> * Yinghai Lu <yhlu.kernel@xxxxxxxxx> wrote:
>> >>
>> >> > [PATCH] x86_64: printout msr
>> >>
>> >> looks rather useful - added it to tip/x86/debug.
>> >
>> > fails to build with the attached config:
>> >
>> > arch/x86/kernel/cpu/common_64.c: In function 'print_cpu_msr':
>> > arch/x86/kernel/cpu/common_64.c:456: error: implicit declaration of function 'rdmsrl_amd_safe'
>> > arch/x86/kernel/cpu/common_64.c: In function 'print_cpu_info':
>> > arch/x86/kernel/cpu/common_64.c:486: error: 'struct cpuinfo_x86' has no member named 'cpu_index'
>> >
>> > i realize that this wasnt sent for inclusion, but i think it would make
>> > sense to tidy it up and integrate it.
>>
>> that was one tool to verify if BIOS does right thing about some special bits.
>>
>> it seems it doesn't compile when xen etc is enable in config.
>
> yeah - but would be nice to fix it, as it's a useful diagnostic patch.
> If people have similar problems in the future they can boot their distro
> kernels with show_mtrr=x to get a MTRR dump.
>

will look at it.

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