From: Brice Goglin <brice@myri.com>
To: Andi Kleen <ak@suse.de>
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: Sat, 17 Jun 2006 10:48:18 -0400 [thread overview]
Message-ID: <44941632.4050703@myri.com> (raw)
In-Reply-To: <p73ver0p4vp.fsf@verdi.suse.de>
Andi Kleen wrote:
> 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
>
IIRC, HT1000 is the southbridge part of the HT2000 chipset. We have been
told that MSI works on this chipset. And from what we've seen/tested, it
is true. The problem is that MSI is often disabled by the BIOS. My
hypertransport MSI capability quirk should check it right.
Brice
next prev parent reply other threads:[~2006-06-17 14:48 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
2006-06-17 14:48 ` Brice Goglin [this message]
[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=44941632.4050703@myri.com \
--to=brice@myri.com \
--cc=ak@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox