All of lore.kernel.org
 help / color / mirror / Atom feed
From: Grant Grundler <grundler@parisc-linux.org>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Matthew Wilcox <matthew@wil.cx>, Brice Goglin <brice@myri.com>,
	linux-pci@atrey.karlin.mff.cuni.cz,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
Date: Mon, 19 Jun 2006 09:27:06 -0600	[thread overview]
Message-ID: <20060619152706.GC7575@colo.lackof.org> (raw)
In-Reply-To: <1150715995.14284.10.camel@capoeira>

On Mon, Jun 19, 2006 at 01:19:55PM +0200, Xavier Bestel wrote:
> On Sat, 2006-06-17 at 07:05, Matthew Wilcox wrote:
> > On Fri, Jun 16, 2006 at 11:01:46PM -0400, Brice Goglin wrote:
> > > We introduce whitelisting of chipsets that are known to support MSI and
> > > keep the existing backlisting to disable MSI for other chipsets. When it
> > > is unknown whether the root chipset support MSI or not, we disable MSI
> > > by default except if pci=forcemsi was passed.
> > 
> > I think that's a bad idea.  Blacklisting is the better idea in the long-term.
> 
> I think the option adopted elsewhere is: whitelist for old chipsets, and
> blacklist for new chipsets. You just have to decide for a good date to
> separate "old" and "new" to minimize the lists size.

I agree with willy.

White lists work "well" only if one's goal is to reduce the number
of bug reports about _all_ HW. Most folks with _working_ MSI (but not
already on the whitelist) won't know they could report this as a bug.
Ie these chipsets likely won't ever get added to the whitelist.

thanks,
grant

  reply	other threads:[~2006-06-19 15:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-17  3:01 [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities Brice Goglin
2006-06-17  5:05 ` Matthew Wilcox
2006-06-17  5:26   ` Brice Goglin
2006-06-19 11:19   ` Xavier Bestel
2006-06-19 15:27     ` Grant Grundler [this message]
2006-06-17  6:28 ` Greg KH
2006-06-17  7:11   ` Brice Goglin
2006-06-17  8:23     ` Andi Kleen
2006-06-17 14:48       ` Brice Goglin
     [not found]         ` <20060619005329.GA1425@greglaptop>
2006-06-19  8:28           ` [discuss] " Andi Kleen
2006-06-19 12:52             ` Brice Goglin
2006-06-19 15:47             ` Greg Lindahl
2006-06-17 11:25   ` Jeff Garzik
2006-06-17 15:34 ` Alistair John Strachan
2006-06-17 16:15   ` Brice Goglin

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=20060619152706.GC7575@colo.lackof.org \
    --to=grundler@parisc-linux.org \
    --cc=brice@myri.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    --cc=xavier.bestel@free.fr \
    /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.