Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1945943AbWJaT6O (ORCPT ); Tue, 31 Oct 2006 14:58:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1945944AbWJaT6N (ORCPT ); Tue, 31 Oct 2006 14:58:13 -0500 Received: from palinux.external.hp.com ([192.25.206.14]:34216 "EHLO mail.parisc-linux.org") by vger.kernel.org with ESMTP id S1945941AbWJaT6M (ORCPT ); Tue, 31 Oct 2006 14:58:12 -0500 Date: Tue, 31 Oct 2006 12:58:11 -0700 From: Matthew Wilcox To: Roland Dreier Cc: "Michael S. Tsirkin" , linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org, jeff@garzik.org, openib-general@openib.org, linux-pci@atrey.karlin.mff.cuni.cz, David Miller Subject: Re: Ordering between PCI config space writes and MMIO reads? Message-ID: <20061031195811.GF26964@parisc-linux.org> References: <20061024214724.GS25210@parisc-linux.org> <20061024223631.GT25210@parisc-linux.org> <20061024.154347.77057163.davem@davemloft.net> <20061031195312.GD5950@mellanox.co.il> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 775 Lines: 15 On Tue, Oct 31, 2006 at 11:53:02AM -0800, Roland Dreier wrote: > > Here's what I don't understand: according to PCI rules, pci config read > > can bypass pci config write (both are non-posted). > > So why does doing it help flush the writes as the comment claims? > > No, I don't believe a read of a config register can pass a write of > the same register. (Someone correct me if I'm wrong) I don't see anything in the PCI spec which forbids it, but I would expect that hardware designers don't actually do that in practice. - 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/