From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751042AbWFTUye (ORCPT ); Tue, 20 Jun 2006 16:54:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751050AbWFTUyd (ORCPT ); Tue, 20 Jun 2006 16:54:33 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:19425 "EHLO mail.dvmed.net") by vger.kernel.org with ESMTP id S1751037AbWFTUyd (ORCPT ); Tue, 20 Jun 2006 16:54:33 -0400 Message-ID: <44986083.9050503@garzik.org> Date: Tue, 20 Jun 2006 16:54:27 -0400 From: Jeff Garzik User-Agent: Thunderbird 1.5.0.4 (X11/20060614) MIME-Version: 1.0 To: Roland Dreier CC: Andi Kleen , Dave Olson , discuss@x86-64.org, Brice Goglin , linux-kernel@vger.kernel.org, gregkh@suse.de Subject: Re: [discuss] Re: [RFC] Whitelist chipsets supporting MSI and check Hyper-transport capabilities References: <200606200925.30926.ak@suse.de> <20060620200352.GJ1414@greglaptop.internal.keyresearch.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -4.2 (----) X-Spam-Report: SpamAssassin version 3.1.3 on srv5.dvmed.net summary: Content analysis details: (-4.2 points, 5.0 required) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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