Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750968AbWIUU5J (ORCPT ); Thu, 21 Sep 2006 16:57:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751525AbWIUU5J (ORCPT ); Thu, 21 Sep 2006 16:57:09 -0400 Received: from sj-iport-5.cisco.com ([171.68.10.87]:45070 "EHLO sj-iport-5.cisco.com") by vger.kernel.org with ESMTP id S1750968AbWIUU5G (ORCPT ); Thu, 21 Sep 2006 16:57:06 -0400 X-IronPort-AV: i="4.09,196,1157353200"; d="scan'208"; a="323922202:sNHT30390248" To: "Bryan O'Sullivan" Cc: Bill Waddington , linux-kernel@vger.kernel.org Subject: Re: Flushing writes to PCI devices X-Message-Flag: Warning: May contain useful information References: <6263h29e4o17ok032m8rv11p4u6547ngk0@4ax.com> <1158862442.29551.22.camel@sardonyx> From: Roland Dreier Date: Thu, 21 Sep 2006 13:56:59 -0700 In-Reply-To: <1158862442.29551.22.camel@sardonyx> (Bryan O'Sullivan's message of "Thu, 21 Sep 2006 11:14:02 -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: 21 Sep 2006 20:57:05.0042 (UTC) FILETIME=[7E618F20:01C6DDC0] Authentication-Results: sj-dkim-5.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: 710 Lines: 17 Bryan> Yes. If your device requires that writes to some locations Bryan> in MMIO space be performed in a specific order, you must Bryan> explicitly do this in your driver. Intel CPUs will flush Bryan> posted writes out of order, for example. Really? Just normal posted PCI writes without using MTRRs or write-combining or anything like that? That doesn't seem right to me, and I would expect all sorts of things to break if it were true. - 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/