Re: [PATCH] x86: cacheinfo: complete L2/L3 Cache and TLBassociativity field definitions

From: Ingo Molnar
Date: Thu Apr 02 2009 - 06:30:40 EST



* Andreas Herrmann <andreas.herrmann3@xxxxxxx> wrote:

> Impact: complete cache information for AMD CPUs
>
> See "CPUID Specification" (AMD Publication #: 25481, Rev. 2.28, April 2008)
>
> Signed-off-by: Andreas Herrmann <andreas.herrmann3@xxxxxxx>
> ---
> arch/x86/kernel/cpu/intel_cacheinfo.c | 16 ++++++++++++----
> 1 files changed, 12 insertions(+), 4 deletions(-)
>
> Please apply.

Hm, the x86/cpu topic is marked broken and blocked by another AMD
patch from Mark Langsdorf:

45ca863: x86, cpu: conform L3 Cache Index Disable to Linux standards

We cannot queue up new patches there before this one is fixed. I've
attached below my last bugreport about it.

Ingo

----- Forwarded message from Ingo Molnar <mingo@xxxxxxx> -----

Date: Thu, 19 Mar 2009 09:18:37 +0100
From: Ingo Molnar <mingo@xxxxxxx>
To: Mark Langsdorf <mark.langsdorf@xxxxxxx>
Subject: Re: [PATCH][retry 5] Conform L3 Cache Index Disable to Linux
Standards
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx,
eric@xxxxxxxxxxxx, hpa@xxxxxxxxx


* Mark Langsdorf <mark.langsdorf@xxxxxxx> wrote:

> Add ABI Documentation entry and fix some /sys directory formating
> issues with the L3 Cache Index Disable feature for future AMD
> processors. Add a check to disable it for family 0x10 models
> that do not support it properly. Correct the disable algorithm
> to reflect erratum 388.
>
> Signed-off-by: Mark Langsdorf <mark.langsdorf@xxxxxxx>

i'm still getting this build failure:

arch/x86/mm/built-in.o:(.bss+0x3640): multiple definition of `k8_northbridges'

i've reported this build failure before. I've excluded this commit
from tip:master for now.

Ingo

----- End forwarded message -----

--
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/