All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
	"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: Wed, 08 Sep 2010 11:51:29 -0700	[thread overview]
Message-ID: <1283971889.18468.13.camel@pjaxe> (raw)
In-Reply-To: <4C87CFFC.8050709@zytor.com>

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

On Wed, 2010-09-08 at 11:03 -0700, H. Peter Anvin wrote:
> On 09/07/2010 11:55 PM, Andi Kleen wrote:
> > "H. Peter Anvin" <hpa@zytor.com> writes:
> >>
> >> If this is a production BIOS it should have this information.
> > 
> > The point was -- it wasn't a production BIOS and the production
> > BIOS will be fixed.
> > 
> 
> From the original description:
> 
> This patch adds a boot parameter to allow a kernel to be booted
> with the option to skip the SRAT check.  There are BIOSes in
>                                          ^^^^^^^^^^^^^^^^^^^
> production that have these failures, so this will allow people
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> in the field to work around these BIOS issues.
> 
> 
> Agreed that command-line option is a good thing to have in general and
> that it is not necessary to have DMI quirks for preproduction BIOSes.

Right.  The new patchset (when I finish it) will have the DMI quirk for
this specific production NHM-EX, plus the command-line option.

-PJ

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4394 bytes --]

      reply	other threads:[~2010-09-08 18:45 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
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 [this message]

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=1283971889.18468.13.camel@pjaxe \
    --to=peter.p.waskiewicz.jr@intel.com \
    --cc=andi@firstfloor.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.