From: Andi Kleen <ak@suse.de>
To: Brice Goglin <brice@myri.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz,
LKML <linux-kernel@vger.kernel.org>,
gregkh@suse.de, discuss@x86-64.org
Subject: Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
Date: 17 Jun 2006 10:23:38 +0200 [thread overview]
Message-ID: <p73ver0p4vp.fsf@verdi.suse.de> (raw)
In-Reply-To: <4493AB39.7010409@myri.com>
Brice Goglin <brice@myri.com> writes:
>
> Or we could enable MSI by default on PCI-E chipsets and disable by
> default on non-PCI-E (ie we whitelist non-PCI-E only) ? PCI-E chipsets
> seem to support MSI pretty well.
It looks like at least Serverworks HT1000 has trouble with MSI
too, but it's PCI-Express. But I guess those can be black listed
Also I think Intel has supported it well for a long time so might
want to white list all from VENDOR == Intel.
Blacklisting all old non PCI-E bridges non Intel seems reasonable
It seems AMD 8132 can be made to work, but it needs a special
quirk too and then it can be white listed.
The rules will be relatively complicated I guess, but should
be doable.
-Andi
next prev parent reply other threads:[~2006-06-17 8:23 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
2006-06-17 7:11 ` Brice Goglin
2006-06-17 8:23 ` Andi Kleen [this message]
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=p73ver0p4vp.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=brice@myri.com \
--cc=discuss@x86-64.org \
--cc=gregkh@suse.de \
--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 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.