From: "H. Peter Anvin" <hpa@zytor.com>
To: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH] [arch-x86] Allow SRAT integrity check to be skipped
Date: Tue, 07 Sep 2010 13:03:47 -0700 [thread overview]
Message-ID: <4C869AA3.6000103@zytor.com> (raw)
In-Reply-To: <1283888337.18468.9.camel@pjaxe>
On 09/07/2010 12:38 PM, Peter P Waskiewicz Jr wrote:
>
> It's one SKU of a Nehalem-EX system. The BIOS for that SKU has an issue
> with resolving SRAT hotplug enumeration, and screws up the table. Other
> SKU's of this same platform do not have the issue. Efforts are underway
> to get this BIOS fixed, but in the meantime, there's nothing for users
> to work around the bug (aside from disabling memory hotplug in the
> BIOS). Another platform almost shipped with the same symptoms, but
> caught it and had it fixed before it shipped (didn't catch it early
> because Windows wasn't failing, and most of the testing on that platform
> was done under Windows).
>
> I agree with Andi that adding DMI strings would be overkill and would
> leave clutter once the BIOS is fixed. I look at this patch as a
> stop-gap measure for people to fall back on until a newer BIOS is
> available to correct the NUMA enumeration issues. Without it, we have
> nothing to point users to when they run into this, waiting for a new
> BIOS.
>
No, this is exactly the kind of stuff for which a DMI match is ideal. A
specific system with bounded propagation of the problem. Thus, the DMI
match acts as a whitelist -- "we know this system and it is safe to
activate this hack on it." This is a very good thing.
If this is a production BIOS it should have this information.
-hpa
next prev parent reply other threads:[~2010-09-07 20:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 21:33 [PATCH] [arch-x86] Allow SRAT integrity check to be skipped Peter P Waskiewicz Jr
2010-09-01 21:33 ` Andi Kleen
2010-09-01 22:04 ` rdunlap
2010-09-01 22:11 ` Peter P Waskiewicz Jr
2010-09-08 19:09 ` H. Peter Anvin
2010-09-03 10:04 ` Andi Kleen
2010-09-02 6:57 ` Ingo Molnar
2010-09-02 10:03 ` Andi Kleen
2010-09-03 6:39 ` Ingo Molnar
2010-09-07 19:38 ` Peter P Waskiewicz Jr
2010-09-07 19:56 ` Ingo Molnar
2010-09-07 20:03 ` H. Peter Anvin [this message]
2010-09-07 20:16 ` Peter P Waskiewicz Jr
2010-09-07 20:48 ` H. Peter Anvin
2010-09-08 6:55 ` Andi Kleen
2010-09-08 18:03 ` H. Peter Anvin
2010-09-08 18:51 ` Peter P Waskiewicz Jr
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=4C869AA3.6000103@zytor.com \
--to=hpa@zytor.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=tglx@linutronix.de \
--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