Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751070AbWJMROJ (ORCPT ); Fri, 13 Oct 2006 13:14:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751408AbWJMROI (ORCPT ); Fri, 13 Oct 2006 13:14:08 -0400 Received: from pentafluge.infradead.org ([213.146.154.40]:56199 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1751070AbWJMROG (ORCPT ); Fri, 13 Oct 2006 13:14:06 -0400 Subject: Re: [linux-pm] Bug in PCI core From: Arjan van de Ven To: Alan Cox Cc: Matthew Wilcox , Adam Belay , Alan Stern , Benjamin Herrenschmidt , Greg KH , linux-pci@atrey.karlin.mff.cuni.cz, Linux-pm mailing list , Kernel development list In-Reply-To: <1160760867.25218.77.camel@localhost.localdomain> References: <1160753187.25218.52.camel@localhost.localdomain> <1160753390.3000.494.camel@laptopd505.fenrus.org> <1160755562.25218.60.camel@localhost.localdomain> <1160757260.26091.115.camel@localhost.localdomain> <1160759349.25218.62.camel@localhost.localdomain> <20061013164933.GD11633@parisc-linux.org> <1160760867.25218.77.camel@localhost.localdomain> Content-Type: text/plain Organization: Intel International BV Date: Fri, 13 Oct 2006 19:13:52 +0200 Message-Id: <1160759632.14815.4.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-2.fc4) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 931 Lines: 22 On Fri, 2006-10-13 at 18:34 +0100, Alan Cox wrote: > Ar Gwe, 2006-10-13 am 10:49 -0600, ysgrifennodd Matthew Wilcox: > > No it didn't. It's undefined behaviour to perform *any* PCI config > > access to the device while it's doing a D-state transition. It may have > > I think you missed the earlier parts of the story - the kernel caches > the base config register state. > > > happened to work with the chips you tried it with, but more likely you > > never hit that window because X simply didn't try to do that. > > Which is why the kernel caches the register state. but... it didn't USE the cache in the case we're protecting here. Instead the hardware would just go splat. - 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/