From: Jeff Garzik <jeff@garzik.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: Andi Kleen <ak@suse.de>, Dave Olson <olson@unixfolk.com>,
discuss@x86-64.org, Brice Goglin <brice@myri.com>,
linux-kernel@vger.kernel.org, gregkh@suse.de
Subject: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities
Date: Tue, 20 Jun 2006 16:54:27 -0400 [thread overview]
Message-ID: <44986083.9050503@garzik.org> (raw)
In-Reply-To: <adaejxjo9ua.fsf@cisco.com>
Roland Dreier wrote:
> However, the other issue is that CONFIG_PCI_MSI forces some other
> changes to x86 interrupt handling, even if no devices will ever use
> MSI. And the changes are such that some systems can't even boot with
> CONFIG_PCI_MSI enabled. This is the more severe problem, which needs
> to be handled if you want distros to turn on MSI.
Agreed. We definitely want CONFIG_PCI_MSI-enabled kernels to work in
all situations.
Jeff
next prev parent reply other threads:[~2006-06-20 20:54 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
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 [this message]
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=44986083.9050503@garzik.org \
--to=jeff@garzik.org \
--cc=ak@suse.de \
--cc=brice@myri.com \
--cc=discuss@x86-64.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=olson@unixfolk.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.