From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <andi@firstfloor.org>
Cc: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] [arch-x86] Allow SRAT integrity check to be skipped
Date: Fri, 3 Sep 2010 08:39:34 +0200 [thread overview]
Message-ID: <20100903063934.GA25863@elte.hu> (raw)
In-Reply-To: <20100902100308.GA17167@basil.fritz.box>
* Andi Kleen <andi@firstfloor.org> wrote:
> > This isnt a particularly useful solution to users of said systems -
> > they have to figure out that this option exists, and then they have
> > to enter this option on the boot line.
>
> This usually only happens in early preproduction systems. So far the
> BIOS always got fixed before they shipped to users.
'Usually' != 'always'. Read the changelog:
' There are BIOSes in production that have these failures, so this will
allow people in the field to work around these BIOS issues. '
Peter, which system in production that has this problem? That one needs
a DMI match.
Preproduction systems can certainly be hacked around with the boot
option and are not worth the DMI match. (preproduction systems also tend
to have have very unspecific DMI strings in most cases - things like
'1234567890' or 'to be filled by OEM')
In important cases a PCI ID match can be done for serious bugs in
widespread preproduction systems - we have a handful of examples in-tree
for such workarounds - but i doubt this is such a case - we use it for
crasher bugs, not for 'boots up slow' cases.
Nevertheless, production systems need a DMI match.
Thanks,
Ingo
next prev parent reply other threads:[~2010-09-03 6:39 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 [this message]
2010-09-07 19:38 ` Peter P Waskiewicz Jr
2010-09-07 19:56 ` Ingo Molnar
2010-09-07 20:03 ` H. Peter Anvin
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=20100903063934.GA25863@elte.hu \
--to=mingo@elte.hu \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).