public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@amd64.org>
To: Boris Ostrovsky <boris.ostrovsky@amd.com>
Cc: Ingo Molnar <mingo@elte.hu>, Boris Ostrovsky <ostr@amd64.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"jvpeetz@web.de" <jvpeetz@web.de>
Subject: Re: [PATCH] Subject: [PATCH] x86, AMD: K8 Rev.A-E processors are subject to erratum 400
Date: Fri, 29 Apr 2011 22:23:38 +0200	[thread overview]
Message-ID: <20110429202338.GA21523@aftab> (raw)
In-Reply-To: <4DBB1B6E.9060203@amd.com>

On Fri, Apr 29, 2011 at 04:11:26PM -0400, Boris Ostrovsky wrote:
> On 04/29/2011 03:55 PM, Ingo Molnar wrote:
> >
> > * Boris Ostrovsky<ostr@amd64.org>  wrote:
> >
> >> Signed-off-by: Boris Ostrovsky<Boris.Ostrovsky@amd.com>
> >> Acked-by: Borislav Petkov<borislav.petkov@amd.com>
> >> Reported-by: Joerg-Volker Peetz<jvpeetz@web.de>
> >> Tested-by: Joerg-Volker Peetz<jvpeetz@web.de>
> >>
> >> 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.
> >
> > Hm, what is the regression, how do users see it? Hangs? Delays? Crashes?
> > Something more benign? The changelog should really contain such information.
> 
> 
> The system becomes unresponsive until an external interrupt (e.g. 
> keyboard input) happens. The most obvious effect is that time is not 
> reported correctly. We haven't seen anything worse but that's probably 
> bad enough.
> 
> Do you want me to resubmit the patch with updated comments?

Yes please. Being too verbose is much better than being laconic with the
commit message.

Also, please put those lines

Signed-off-by: Boris Ostrovsky <Boris.Ostrovsky@amd.com>
Acked-by: Borislav Petkov <borislav.petkov@amd.com>
Reported-by: Joerg-Volker Peetz <jvpeetz@web.de>
Tested-by: Joerg-Volker Peetz <jvpeetz@web.de>

_after_ the commit message.

Thanks.

-- 
Regards/Gruss,
Boris.

Operating Systems Research Center
Advanced Micro Devices, Inc.

  reply	other threads:[~2011-04-29 20:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-29 19:51 [PATCH] Subject: [PATCH] x86, AMD: K8 Rev.A-E processors are subject to erratum 400 Boris Ostrovsky
2011-04-29 19:55 ` Ingo Molnar
2011-04-29 20:11   ` Boris Ostrovsky
2011-04-29 20:23     ` Borislav Petkov [this message]
2011-04-29 20:35       ` Jiri Slaby

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=20110429202338.GA21523@aftab \
    --to=bp@amd64.org \
    --cc=boris.ostrovsky@amd.com \
    --cc=jvpeetz@web.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=ostr@amd64.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox