| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20110429195548.GA17166@elte.hu> Date: Fri, 29 Apr 2011 21:55:48 +0200 From: Ingo Molnar <mingo@...e.hu> To: Boris Ostrovsky <ostr@...64.org> Cc: x86@...nel.org, linux-kernel@...r.kernel.org, jvpeetz@....de, borislav.petkov@....com, boris.ostrovsky@....com Subject: Re: [PATCH] Subject: [PATCH] x86, AMD: K8 Rev.A-E processors are subject to erratum 400 * Boris Ostrovsky <ostr@...64.org> wrote: > Signed-off-by: Boris Ostrovsky <Boris.Ostrovsky@....com> > Acked-by: Borislav Petkov <borislav.petkov@....com> > Reported-by: Joerg-Volker Peetz <jvpeetz@....de> > Tested-by: Joerg-Volker Peetz <jvpeetz@....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. Thanks, Ingo -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists