Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423763AbWJaWa3 (ORCPT ); Tue, 31 Oct 2006 17:30:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1423762AbWJaWa2 (ORCPT ); Tue, 31 Oct 2006 17:30:28 -0500 Received: from sj-iport-4.cisco.com ([171.68.10.86]:63559 "EHLO sj-iport-4.cisco.com") by vger.kernel.org with ESMTP id S1423724AbWJaWa1 (ORCPT ); Tue, 31 Oct 2006 17:30:27 -0500 To: Matthew Wilcox , John Partridge Cc: "Richard B. Johnson" , "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? X-Message-Flag: Warning: May contain useful information References: <20061024214724.GS25210@parisc-linux.org> <20061024223631.GT25210@parisc-linux.org> <20061024.154347.77057163.davem@davemloft.net> <20061031195312.GD5950@mellanox.co.il> <019301c6fd2c$044d7010$0732700a@djlaptop> <20061031204717.GG26964@parisc-linux.org> From: Roland Dreier Date: Tue, 31 Oct 2006 14:30:13 -0800 In-Reply-To: <20061031204717.GG26964@parisc-linux.org> (Matthew Wilcox's message of "Tue, 31 Oct 2006 13:47:17 -0700") Message-ID: User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.18 (linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-OriginalArrivalTime: 31 Oct 2006 22:30:15.0077 (UTC) FILETIME=[22D33550:01C6FD3C] Authentication-Results: sj-dkim-6.cisco.com; header.From=rdreier@cisco.com; dkim=pass ( sig from cisco.com verified; ); Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 847 Lines: 19 > I'm beginning to think Michael Tsirkin has the only solution to this > -- architectures need to check that their hardware blocks until the > config write completion has occurred (and if not, simulate that it has > in software). OK, I guess I'm convinced. The vague language in the base PCI 3.0 spec about "dependencies" made me think that a read of a config register had to wait until all previous writes to the same register are done. So I'll drop this patch for now. John, you'll need to try and come up with a way to solve this in the Altix implementation of pci_write_config_xxx(). - R. - 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/