From: Andi Kleen <ak@suse.de>
To: "Nakajima, Jun" <jun.nakajima@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Options for handling buggy PCI/PCI-X hardware when MSI is enabled
Date: 17 Sep 2003 01:45:38 +0200 [thread overview]
Message-ID: <p73ekygnvq5.fsf@oldwotan.suse.de> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D3720017304AF60@scsmsx402.sc.intel.com.suse.lists.linux.kernel>
"Nakajima, Jun" <jun.nakajima@intel.com> writes:
> "Blacklist" approach using PCI_quirks.c
> ---------------------------------------
> Pros
> - Places the burden to fix broken HW on the HW owners
> - Consistent with the current MSI patch (enable all by default)
> - A simple fix and minimum patch size (Patch already exists)
> Cons
> - Core kernel impact (larger image size)
And worse one has to submit patches for the core kernel all the time.
And it's a single table, which means there will be lots of conflicts
when merging patches.
I think the new API approach is much better. Best would be if there
was a relatively simple standard way to add it to drivers (like a
standard module option). Then one could add it to a lot of drivers
with default to off. Users can test then and if it works the default
can be changed.
-Andi
next parent reply other threads:[~2003-09-16 23:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7F740D512C7C1046AB53446D3720017304AF60@scsmsx402.sc.intel.com.suse.lists.linux.kernel>
2003-09-16 23:45 ` Andi Kleen [this message]
2003-09-17 0:02 ` Options for handling buggy PCI/PCI-X hardware when MSI is enabled Zwane Mwaikambo
2003-09-16 21:26 Nakajima, Jun
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=p73ekygnvq5.fsf@oldwotan.suse.de \
--to=ak@suse.de \
--cc=jun.nakajima@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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