All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: "Jörg-Volker Peetz" <jvpeetz@web.de>
Cc: Borislav Petkov <bp@amd64.org>,
	Nick Bowler <nbowler@elliptictech.com>,
	"Ostrovsky, Boris" <Boris.Ostrovsky@amd.com>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@amd.com>,
	Greg Kroah-Hartman <greg@kroah.com>,
	"Rosenfeld, Hans" <Hans.Rosenfeld@amd.com>,
	X86-ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] AMD ARAT fixes
Date: Tue, 17 May 2011 18:53:18 +0200	[thread overview]
Message-ID: <20110517165318.GH30053@aftab> (raw)
In-Reply-To: <4DD2A496.8000407@web.de>

On Tue, May 17, 2011 at 12:38:46PM -0400, Jörg-Volker Peetz wrote:
> A kernel version 2.6.38.6 patched with your two patches modifying only
> arch/x86/kernel/cpu/amd.c starts and runs without problems on the affected
> system with a AMD Turion 64 processor. The system is pure x86_64 (Debian
> Release: wheezy/sid) with gcc version 4.6.1 20110428 (prerelease) (Debian
> 4.6.0-6) and GNU C Library (Debian EGLIBC 2.13-4) stable release version 2.13.

Thanks for testing!

> The only obvious difference I see is the message "using C1E aware idle routine"
> in dmesg.

That was your CPU, right:

vendor_id       : AuthenticAMD
cpu family      : 15
model           : 36
model name      : AMD Turion(tm) 64 Mobile Technology MT-40
stepping        : 2

?

If so, then the C1E idle line above shouldn't appear. Can you check that
around line 698 in <arch/x86/kernel/cpu/amd.c> you have the following:

 const int amd_erratum_400[] =
       AMD_OSVW_ERRATUM(1, AMD_MODEL_RANGE(0xf, 0x41, 0x2, 0xff, 0xf),
                           AMD_MODEL_RANGE(0x10, 0x2, 0x1, 0xff, 0xf));

On your machine, you should be using the default_idle routine instead,
since you don't have C1E.

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2011-05-17 16:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-17 12:55 [PATCH 0/2] AMD ARAT fixes Borislav Petkov
2011-05-17 12:55 ` [PATCH 1/2] Revert "x86, AMD: Fix APIC timer erratum 400 affecting K8 Rev.A-E processors" Borislav Petkov
2011-05-17 12:55 ` [PATCH 2/2] x86, AMD: Fix ARAT feature setting again Borislav Petkov
2011-05-17 13:47   ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2011-05-17 16:38 ` [PATCH 0/2] AMD ARAT fixes Jörg-Volker Peetz
2011-05-17 16:53   ` Borislav Petkov [this message]
2011-05-17 17:21     ` Jörg-Volker Peetz
2011-05-17 17:46       ` Borislav Petkov
2011-05-17 17:51         ` Jörg-Volker Peetz
2011-05-17 18:01           ` Borislav Petkov
2011-05-17 22:30 ` Nick Bowler
2011-05-18  6:51   ` Borislav Petkov
2011-05-18 15:50 ` Borislav Petkov
2011-05-20 14:37   ` Chuck Ebbert
2011-05-20 18:10     ` Boris Ostrovsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110517165318.GH30053@aftab \
    --to=bp@amd64.org \
    --cc=Andreas.Herrmann3@amd.com \
    --cc=Boris.Ostrovsky@amd.com \
    --cc=Hans.Rosenfeld@amd.com \
    --cc=greg@kroah.com \
    --cc=jvpeetz@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nbowler@elliptictech.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.