Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965207AbWJXVYw (ORCPT ); Tue, 24 Oct 2006 17:24:52 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965206AbWJXVYw (ORCPT ); Tue, 24 Oct 2006 17:24:52 -0400 Received: from outpipe-village-512-1.bc.nu ([81.2.110.250]:57528 "EHLO lxorguk.ukuu.org.uk") by vger.kernel.org with ESMTP id S965205AbWJXVYv (ORCPT ); Tue, 24 Oct 2006 17:24:51 -0400 Subject: Re: Ordering between PCI config space writes and MMIO reads? From: Alan Cox To: Roland Dreier Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, openib-general@openib.org, John Partridge In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 24 Oct 2006 22:24:23 +0100 Message-Id: <1161725063.22348.39.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 (2.6.2-1.fc5.5) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 782 Lines: 16 Ar Maw, 2006-10-24 am 12:13 -0700, ysgrifennodd Roland Dreier: > 1) Is this something that should be fixed in the driver? The PCI > spec allows MMIO cycles to start before an earlier config cycle > completed, but do we want to expose this fact to drivers? Would > it be better for ia64 to use some sort of barrier to make sure > pci_write_config_xxx() is strongly ordered with MMIO? It is good to be conservative in this area. Some AMD chipsets at least had ordering problems with some configurations in the K7 era. - 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/