From: Borislav Petkov <bp@alien8.de>
To: Dave Jones <davej@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Dave Hansen <dave@sr71.net>,
linux-kernel@vger.kernel.org, x86@kernel.org,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [RFC][PATCH 3/3] x86: make MP a required-feature on 64-bit
Date: Fri, 20 Jun 2014 20:48:39 +0200 [thread overview]
Message-ID: <20140620184839.GI11391@pd.tnic> (raw)
In-Reply-To: <20140620181600.GA1331@redhat.com>
On Fri, Jun 20, 2014 at 02:16:00PM -0400, Dave Jones wrote:
> AMD sold two separate SKUs: the Athlon XP and the Athlon MP.
> Only the latter was supposedly "certified" for use in multi-processor
> boards. People found out however that sometimes the XP's 'worked'
> if you modded them (see http://www.hardwaresecrets.com/article/How-to-Transform-an-Athlon-XP-into-an-Athlon-MP/24)
Haha, that was a fun read. Closing fuses with a pencil - this reminds me
of:
https://www.youtube.com/watch?v=6QihBIewyrY
> I doubt anyone is actually even running such a system any more on
> a modern kernel, and any weird crashes would be written off more by
> "you're running 10+ year old hardware, it's probably broken" than
> "it was never meant to do that".
Yeah, we can kill amd_k7_smp_check() but I don't see why - it doesn't
hurt anyone right now. I don't care all that much either way, though -
whatever.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-06-20 18:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-20 16:17 [RFC][PATCH 1/3] x86: introduce disabled-features Dave Hansen
2014-06-20 16:17 ` [RFC][PATCH 2/3] x86: add more disabled features Dave Hansen
2014-06-20 16:17 ` [RFC][PATCH 3/3] x86: make MP a required-feature on 64-bit Dave Hansen
2014-06-20 16:23 ` H. Peter Anvin
2014-06-20 16:30 ` Dave Hansen
2014-06-20 16:37 ` H. Peter Anvin
2014-06-20 17:43 ` Borislav Petkov
2014-06-20 17:47 ` H. Peter Anvin
2014-06-20 18:05 ` Borislav Petkov
2014-06-20 18:16 ` Dave Jones
2014-06-20 18:48 ` Borislav Petkov [this message]
2014-06-20 18:54 ` H. Peter Anvin
2014-06-20 20:00 ` Borislav Petkov
2014-06-20 20:22 ` H. Peter Anvin
2014-06-20 20:35 ` Borislav Petkov
2014-06-20 17:50 ` H. Peter Anvin
2014-06-20 18:15 ` Borislav Petkov
2014-06-20 18:57 ` H. Peter Anvin
2014-06-20 20:37 ` Borislav Petkov
2014-06-23 6:11 ` Andi Kleen
2014-06-20 16:20 ` [RFC][PATCH 1/3] x86: introduce disabled-features H. Peter Anvin
2014-06-20 17:20 ` Dave Hansen
2014-06-20 20:40 ` Dave Hansen
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=20140620184839.GI11391@pd.tnic \
--to=bp@alien8.de \
--cc=ak@linux.intel.com \
--cc=dave@sr71.net \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).