public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Brice Goglin <brice@myri.com>
Cc: 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: Fri, 16 Jun 2006 23:28:40 -0700	[thread overview]
Message-ID: <20060617062840.GD31645@kroah.com> (raw)
In-Reply-To: <4493709A.7050603@myri.com>

On Fri, Jun 16, 2006 at 11:01:46PM -0400, Brice Goglin wrote:
> Several chipsets are known to not support MSI. Some support MSI but
> disable it by default. Thus, several drivers implement their own way to
> detect whether MSI works.
> 
> 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.
> 
> Whitelisting is done by setting a new PCI_BUS_FLAGS_MSI in the chipset
> subordinate bus. pci_enable_msi() thus starts by checking whether the
> root chipset of the device has the MSI or NOMSI flag set.

Whitelisting looks all well and good today, and maybe for the rest of
the year.  But what about 3 years from now when everyone has shaken all
of the MSI bugs out of their chipsets finally?  Do you really want to
add a new quirk for _every_ new chipset that comes out?  I don't think
that it is managable over the long run.

I do like your checks to see if MSI is able to be enabled or not, and
maybe we can just invert them to mark those chips that do not support
MSI today?

> I do not split this patch in multiple pieces since it is still small
> and this is just a RFC. I will split it for the actual submission.

Please do, you are doing a lot of different things in here.

thanks,

greg k-h

  parent reply	other threads:[~2006-06-17  6:31 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
2006-06-17  6:28 ` Greg KH [this message]
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=20060617062840.GD31645@kroah.com \
    --to=greg@kroah.com \
    --cc=brice@myri.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    /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