From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] ALSA: hda-intel - Disable MSI support by default]
Date: Thu, 16 Nov 2006 11:04:41 +0100 [thread overview]
Message-ID: <455C37B9.4020000@ens-lyon.org> (raw)
(forgot to cc: LKML)
Roland Dreier wrote:
> > A whitelist is an awkward solution, the problem is the number of
> > chipsets available with MSI will continue to grow. And the assumption
> > is that after Microsoft OS supports MSI, that newer chipsets will work.
>
> Maybe a whitelist for older systems and then enable everything after a
> DMI cutoff date by default? Doesn't work on non-PC stuff though...
When I started sending patches about all this, I proposed a whitelist
for PCI bridges and a blacklist for PCIe bridges, but Greg was against
whitelisting.
Now, reading this thread, I am very disturbed with the idea of disabling
MSI on all non-Intel bridges. Blacklisting correctly shouldn't be that
hard. From my point of view, there are several non-Intel bridges that
seem to support MSI very well (especially some HT<->PCIe bridges). And
apart from being required for ipath, MSI improves the performance of
network drivers a bit, so I'd rather keep it enabled on trusted bridges...
Brice
reply other threads:[~2006-11-16 10:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=455C37B9.4020000@ens-lyon.org \
--to=brice.goglin@ens-lyon.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
/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
all inboxes | Powered by JetHome®