From: Borislav Petkov <bp@alien8.de>
To: Dave Jones <davej@redhat.com>
Cc: "H. Peter Anvin" <hpa@linux.intel.com>,
Fengguang Wu <fengguang.wu@intel.com>,
Ingo Molnar <mingo@kernel.org>,
Yinghai Lu <yhlu.kernel@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [qemu64,+smep,+smap] WARNING: CPU: 1 PID: 0 at arch/x86/kernel/cpu/amd.c:220 init_amd()
Date: Fri, 7 Mar 2014 23:39:29 +0100 [thread overview]
Message-ID: <20140307223929.GI5255@pd.tnic> (raw)
In-Reply-To: <20140307222743.GC580@redhat.com>
On Fri, Mar 07, 2014 at 05:27:43PM -0500, Dave Jones wrote:
> When I wrote it 10 years or so back it made more sense than it
> probably does now, so I'd be ok with just dropping it all too tbh.
> Machines of that vintage probably have bigger problems now anyway.
Yeah.
> I don't recall seeing a report of the taint flag being set ever in
> a Red Hat bug report, but we've seen countless problems from machines
> of that era with dying ram or motherboard capacitors or..
Right, this should be a sufficient indicator that those machines won't
be running modern kernels anymore :-)
Oh, and besides, this really frees up that taint bit TAINT_UNSAFE_SMP
for the forcepae thing. Let me cook up a patch - it looks like 3.14
will be the release where we're getting rid of old platforms - look at
tip/x86/nuke-platforms. :-)
> I still have NexGen docs somewhere ;)
Uuuh, more than ancient, make sure to hold on to those :-)
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-03-07 22:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 1:58 Fengguang Wu
2014-03-07 5:03 ` H. Peter Anvin
2014-03-07 5:50 ` Fengguang Wu
2014-03-07 18:56 ` H. Peter Anvin
2014-03-07 19:10 ` Dave Jones
2014-03-07 21:01 ` H. Peter Anvin
2014-03-07 21:38 ` Borislav Petkov
2014-03-07 22:06 ` Dave Jones
2014-03-07 22:11 ` H. Peter Anvin
2014-03-07 22:22 ` Dave Jones
2014-03-07 22:27 ` Fengguang Wu
2014-03-07 22:34 ` Borislav Petkov
2014-03-07 22:20 ` Borislav Petkov
2014-03-07 22:27 ` Dave Jones
2014-03-07 22:39 ` Borislav Petkov [this message]
2014-03-09 18:07 ` Paolo Bonzini
2014-03-09 18:50 ` Borislav Petkov
2014-03-10 0:01 ` H. Peter Anvin
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=20140307223929.GI5255@pd.tnic \
--to=bp@alien8.de \
--cc=davej@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=yhlu.kernel@gmail.com \
/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
Powered by JetHome