From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750841AbWFTUED (ORCPT ); Tue, 20 Jun 2006 16:04:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750852AbWFTUED (ORCPT ); Tue, 20 Jun 2006 16:04:03 -0400 Received: from mx.pathscale.com ([64.160.42.68]:28373 "EHLO mx.pathscale.com") by vger.kernel.org with ESMTP id S1750841AbWFTUEB (ORCPT ); Tue, 20 Jun 2006 16:04:01 -0400 Date: Tue, 20 Jun 2006 13:03:52 -0700 From: Greg Lindahl To: Andi Kleen Cc: 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 Message-ID: <20060620200352.GJ1414@greglaptop.internal.keyresearch.com> Mail-Followup-To: Andi Kleen , Dave Olson , discuss@x86-64.org, Brice Goglin , linux-kernel@vger.kernel.org, gregkh@suse.de References: <200606200925.30926.ak@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200606200925.30926.ak@suse.de> User-Agent: Mutt/1.4.1i X-Frumious: Bandersnatch Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 20, 2006 at 09:25:30AM +0200, Andi Kleen wrote: > 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? You probably meant the other Greg, but the situation doesn't seem to be that bad. Brice's proposed whitelist covers almost all Opteron PCI Express servers. What is the list of things which are known to have problems? All PCI-X? We can ask some more people with PCI-X MSI cards what works for them, i.e. Mellanox. -- greg