All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
	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 08:55:18 +0200	[thread overview]
Message-ID: <87wrqwiv1l.fsf@basil.nowhere.org> (raw)
In-Reply-To: <4C869AA3.6000103@zytor.com> (H. Peter Anvin's message of "Tue, 07 Sep 2010 13:03:47 -0700")

"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.

If you want you call fill the DMI tables with all bugs in preproduction
BIOS, but I suspect that will fill them up rather quickly. Preproduction
BIOS tend to be buggy (that is why they are pre-production)

Another problem also with adding stuff for early BIOS is that the later
BIOS likely have this fixed and then you have a quirk that runs but is
not needed (unless you add another DMI match for the fixed production
BIOS etc.) While for this case it would be probably harmless, 
this has caused problems in the past with other quirks.

Normally early users are also ok with having to specify an option
as a workaround, they just need something they can specify.

IMHO also it's good coding practice to have a command line option
for every DMI quirk anyways. This makes it easier to let 
users test if they need a particular quirk and helps
with users running older kernels.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  parent reply	other threads:[~2010-09-08  6:55 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 [this message]
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=87wrqwiv1l.fsf@basil.nowhere.org \
    --to=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=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 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.