From: Tim Hockin <thockin@hockin.org>
To: Ross Biro <ross.biro@gmail.com>
Cc: Dave Jones <davej@redhat.com>, Andi Kleen <ak@muc.de>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC/Patch 2.6.11] Take control of PCI Master Abort Mode
Date: Thu, 14 Apr 2005 10:34:38 -0700 [thread overview]
Message-ID: <20050414173438.GA9488@hockin.org> (raw)
In-Reply-To: <8783be66050414102551698d86@mail.gmail.com>
On 4/13/05, Dave Jones <davej@redhat.com> wrote:
> If we have a situation where we screw a subset of users with the
> config option =y and a different subset with =n, how is this improving
> the situation any over what we have today ?
Dave,
What's a good alternative? Do we need to keep a whitelist of hardware
that is known to work? A blacklist is pretty risky, since this is a very
hard problem to find.
What if it was always on, except when the commandlien was passed
(eliminate the CONFIG option)? Really 'leet hacks could tweak a #define
if they don't like the command line option..
next prev parent reply other threads:[~2005-04-14 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-05 19:33 [RFC/Patch 2.6.11] Take control of PCI Master Abort Mode Ross Biro
2005-04-05 20:53 ` Randy.Dunlap
2005-04-06 12:47 ` Ross Biro
2005-04-06 20:44 ` Daniel Egger
2005-04-10 13:29 ` Andi Kleen
[not found] ` <8783be66050412075218b2b0b0@mail.gmail.com>
2005-04-13 18:37 ` Andi Kleen
2005-04-13 23:00 ` Ross Biro
2005-04-13 23:28 ` Dave Jones
2005-04-14 17:25 ` Ross Biro
2005-04-14 17:34 ` Tim Hockin [this message]
2005-04-14 18:02 ` Andi Kleen
2005-04-14 18:33 ` Dave Jones
2005-04-14 19:14 ` Daniel Egger
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=20050414173438.GA9488@hockin.org \
--to=thockin@hockin.org \
--cc=ak@muc.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.biro@gmail.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