Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760923Ab1D2Txc (ORCPT ); Fri, 29 Apr 2011 15:53:32 -0400 Received: from s15228384.onlinehome-server.info ([87.106.30.177]:44086 "EHLO mail.x86-64.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755983Ab1D2Txb (ORCPT ); Fri, 29 Apr 2011 15:53:31 -0400 From: Boris Ostrovsky To: x86@kernel.org Cc: linux-kernel@vger.kernel.org, jvpeetz@web.de, borislav.petkov@amd.com, boris.ostrovsky@amd.com Subject: [PATCH] Subject: [PATCH] x86, AMD: K8 Rev.A-E processors are subject to erratum 400 Date: Fri, 29 Apr 2011 15:51:03 -0400 Message-Id: <1304106663-3720-1-git-send-email-ostr@amd64.org> X-Mailer: git-send-email 1.7.3.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1419 Lines: 36 Signed-off-by: Boris Ostrovsky Acked-by: Borislav Petkov Reported-by: Joerg-Volker Peetz Tested-by: Joerg-Volker Peetz Older AMD K8 processors (Revisions A-E) are affected by erratum 400 (APIC timer interrupts don't occur in C states greater than C1). This, for example, means that X86_FEATURE_ARAT flag should not be set for these parts. This addresses regression introduced by commit b87cf80af3ba4b4c008b4face3c68d604e1715c6 (x86, AMD: Set ARAT feature on AMD processors") so it is somewhat high priority. --- arch/x86/kernel/cpu/amd.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/arch/x86/kernel/cpu/amd.c b/arch/x86/kernel/cpu/amd.c index 3532d3b..71499b4 100644 --- a/arch/x86/kernel/cpu/amd.c +++ b/arch/x86/kernel/cpu/amd.c @@ -698,7 +698,7 @@ cpu_dev_register(amd_cpu_dev); */ const int amd_erratum_400[] = - AMD_OSVW_ERRATUM(1, AMD_MODEL_RANGE(0xf, 0x41, 0x2, 0xff, 0xf), + AMD_OSVW_ERRATUM(1, AMD_MODEL_RANGE(0xf, 0x4, 0x2, 0xff, 0xf), AMD_MODEL_RANGE(0x10, 0x2, 0x1, 0xff, 0xf)); EXPORT_SYMBOL_GPL(amd_erratum_400); -- 1.7.3.4 -- 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/