Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1765610AbXIMTXB (ORCPT ); Thu, 13 Sep 2007 15:23:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754359AbXIMTWx (ORCPT ); Thu, 13 Sep 2007 15:22:53 -0400 Received: from rv-out-0910.google.com ([209.85.198.190]:62454 "EHLO rv-out-0910.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753997AbXIMTWw (ORCPT ); Thu, 13 Sep 2007 15:22:52 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OxI6/l9ppvLOM3p0kf0A6YAXTgJ35juNFFKCgRBTWmoLsytojRVz15aRxnyvmyFLMaWU2xFz9M7dEDuV8kwJNOFfx86NAyRHTlQsxr8vRRZGaztis6YmnK1AjtVdrUCls+RjbX1lcUfQeJJuGoRehjhVzQ4z3p9RjqoemG5opOQ= Message-ID: <86802c440709131222v6e819e4ayed27430ba4e61154@mail.gmail.com> Date: Thu, 13 Sep 2007 12:22:51 -0700 From: "Yinghai Lu" To: "H. Peter Anvin" Subject: Re: [PATCH] x86_64: set cfg_size for AMD Family 10h in case MMCONFIG is used Cc: "Andi Kleen" , "Greg KH" , "Andrew Morton" , "Jeff Garzik" , "Martin Mares" , "dean gaudet" , "Robert Richter" , "Linux Kernel Mailing List" In-Reply-To: <46E97178.2040903@zytor.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200709121921.43950.yinghai.lu@sun.com> <200709131147.43446.ak@suse.de> <20070913104704.GA3878@kroah.com> <200709131353.15752.ak@suse.de> <86802c440709131001w4b758921r52a23f1732a6e9c8@mail.gmail.com> <46E97178.2040903@zytor.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1246 Lines: 28 On 9/13/07, H. Peter Anvin wrote: > Yinghai Lu wrote: > > > > BIOS guys also said that fam 10h need mmconfig via eax accessing, may > > need OS do sth, so it is safe to stay with MCFG entry for SB like > > mcp55... > > > > but latest kernel already have that workaround to make mmconfig via eax... > > > > This is actually a good point. Since the CPU vendor managed to > completely fuck up the operation of MMCONFIG itself on this CPU (it's a > *MEMORY REFERENCE*, guys!), it is actually to be expected and prudent > that BIOS vendors will drop the MCFG entry. MMCONFIG doesn't actually > work on this CPU for any system software which doesn't already know to > work around this particular piece of severe braindamage; > standards-complicant MMCONFIG isn't supported at all. if other mmconfig device on x86 is sick of accessing via eax, may need to provide one fam10h_pci_mmcfg to be assigned to raw_pci_ops instead and leave pci_mmcfg to default behavior ( *MEMORY REFERENCE*). YH - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/