From: Chuck Ebbert <cebbert@redhat.com>
To: Hans Rosenfeld <hans.rosenfeld@amd.com>
Cc: "Ostrovsky, Boris" <Boris.Ostrovsky@amd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>
Subject: Re: [PATCH] cpu, AMD: Fix another bug in the new errata checking code
Date: Mon, 16 May 2011 08:43:51 -0400 [thread overview]
Message-ID: <20110516084351.003bb214@katamari> (raw)
In-Reply-To: <20110513151921.GA878@escobedo.osrc.amd.com>
On Fri, 13 May 2011 17:19:23 +0200
Hans Rosenfeld <hans.rosenfeld@amd.com> wrote:
> > > > Could you send me the contents of MSRs 0xc0010140, 0xc0010141 and
> > > > 0xc0010055?
> > >
> > > Knowing whether any C state above C1 is declared could be useful too.
> > >
> > rdmsr 0xc0010140 gives 2
>
> This means that E400 is known ...
>
> > rdmsr 0xc0010141 gives 0
>
> ... and no workaround is necessary ...
>
> > rdmsr 0xc0010055 gives 0
>
> ... because C1E is not enabled.
>
> > And ARAT is definitely set where it wasn't before these updates.
>
> I don't see how that could possibly make a difference if C1E is not even
> enabled. This is all very strange.
>
Looking at commit e20a2d205c05cef6b5783df339a7d54adeb50962 ("x86, AMD: Fix
APIC timer erratum 400 affecting K8 Rev.A-E processors") I see that it
extended the E400 workaround to cover a whole range of processors that
have never supported C1E. Isn't this just more of the same problem, only
happening with processors that support C1E but have it disabled?
They are using C3 for idle states, I can confirm that now.
next prev parent reply other threads:[~2011-05-16 12:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 23:59 [PATCH] cpu, AMD: Fix another bug in the new errata checking code Chuck Ebbert
2011-05-13 10:21 ` Hans Rosenfeld
2011-05-13 13:03 ` Boris Ostrovsky
2011-05-13 14:59 ` Chuck Ebbert
2011-05-13 15:19 ` Hans Rosenfeld
2011-05-16 12:43 ` Chuck Ebbert [this message]
2011-05-16 13:38 ` 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=20110516084351.003bb214@katamari \
--to=cebbert@redhat.com \
--cc=Boris.Ostrovsky@amd.com \
--cc=Borislav.Petkov@amd.com \
--cc=hans.rosenfeld@amd.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox