Upstream fixes for this:
commit b6734c35af028f06772c0b2c836c7d579e6d4dad
Author: H. Peter Anvin <hpa@zytor.com>
Date: Mon Aug 18 17:39:32 2008 -0700
x86: add NOPL as a synthetic CPU feature bit
The long noops ("NOPL") are supposed to be detected by family >= 6.
Unfortunately, several non-Intel x86 implementations, both hardware
and software, don't obey this dictum. Instead, probe for NOPL
directly by executing a NOPL instruction and see if we get #UD.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
commit f31d731e4467e61de51d7f6d7115f3b712d9354c
Author: H. Peter Anvin <hpa@zytor.com>
Date: Mon Aug 18 17:50:33 2008 -0700
x86: use X86_FEATURE_NOPL in alternatives
Use X86_FEATURE_NOPL to determine if it is safe to use P6 NOPs in
alternatives. Also, replace table and loop with simple if statement.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
commit ba0593bf553c450a03dbc5f8c1f0ff58b778a0c8
Author: H. Peter Anvin <hpa@zytor.com>
Date: Tue Sep 16 09:29:40 2008 -0700
x86: completely disable NOPL on 32 bits
Completely disable NOPL on 32 bits. It turns out that Microsoft
Virtual PC is so broken it can't even reliably *fail* in the presence
of NOPL.
This leaves the infrastructure in place but disables it
unconditionally.
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part