public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Dave Olson <olson@unixfolk.com>
Cc: discuss@x86-64.org, Brice Goglin <brice@myri.com>,
	linux-kernel@vger.kernel.org,
	Greg Lindahl <greg.lindahl@qlogic.com>,
	gregkh@suse.de
Subject: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
Date: Tue, 20 Jun 2006 09:25:30 +0200	[thread overview]
Message-ID: <200606200925.30926.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0606192237560.25433@osa.unixfolk.com>


> Sure, that's true of almost everything new.   It remains broken until people
> start using it, complain, and get the bugs fixed.   Some of us have a vested
> interest in having MSI work, since it's the only way we can deliver interrupts.
> We've already worked with a few BIOS writers to get problems fixed, and we'll
> keep doing so as we find problems.   If enough hardware vendors and consumers
> do so, the broken stuff will get fixed, and stay fixed, because it will get
> tested.

Sometimes there are new things that work relatively well and only break occassionally
and then there are things where it seems to be the other way round.

My point was basically that every time we tried to turn on such a banana green feature
without white listing it was a sea of pain to get it to work everywhere
and tended to cause far too many non boots

(and any non boot is far worse than whatever performance advantage you get
from it) 

So if there are any more MSI problems comming up IMHO it should be white list/disabled 
by default and only turn on after a long time when Windows uses it by default 
or something. Greg, do you agree?

-Andi

  reply	other threads:[~2006-06-20  7:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.5FgZbVFZIyOdjQ3utdNvbqTrUq0@ifi.uio.no>
     [not found] ` <fa.URgTUhhO9H/aLp98XyIN2gzSppk@ifi.uio.no>
2006-06-20  5:42   ` [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities Dave Olson
2006-06-20  7:25     ` Andi Kleen [this message]
2006-06-20  8:02       ` Jeff Garzik
2006-06-20  8:13         ` Andi Kleen
2006-06-20  8:27           ` Jeff Garzik
2006-06-20 22:44             ` Eric W. Biederman
2006-06-20 20:03       ` Greg Lindahl
2006-06-20 20:20         ` Randy.Dunlap
2006-06-20 20:26           ` Brice Goglin
2006-06-20 20:41           ` Greg Lindahl
2006-06-20 20:50             ` Brice Goglin
2006-06-20 20:53               ` Jeff Garzik
2006-06-20 20:57               ` Dave Olson
2006-06-20 20:23         ` Roland Dreier
2006-06-20 20:54           ` Jeff Garzik
2006-06-20 21:29       ` Greg KH
2006-06-20 22:27         ` Brice Goglin
2006-06-20 23:05           ` Greg KH
2006-06-20 23:16             ` Brice Goglin
2006-06-20 22:33         ` [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilitiesKJ Andi Kleen
2006-06-20 22:46           ` Roland Dreier
2006-06-21  6:19             ` Dave Olson
2006-06-17  3:01 [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities Brice Goglin
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

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=200606200925.30926.ak@suse.de \
    --to=ak@suse.de \
    --cc=brice@myri.com \
    --cc=discuss@x86-64.org \
    --cc=greg.lindahl@qlogic.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olson@unixfolk.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