To: linux-kernel@vger.kernel.org
From: "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] Document Linux's memory barriers
Date: Thu, 9 Mar 2006 16:49:01 -0800 (PST)
Organization: Mostly alphabetical, except Q, with we do not fancy
Message-ID: <duqidt$erm$1@terminus.zytor.com>
References: <17422.19209.60360.178668@cargo.ozlabs.ibm.com> <31492.1141753245@warthog.cambridge.redhat.com> <28393.1141823992@warthog.cambridge.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
NNTP-Posting-Date: Fri, 10 Mar 2006 00:49:01 +0000 (UTC)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 842
Lines: 22

Followup to:  <28393.1141823992@warthog.cambridge.redhat.com>
By author:    David Howells <dhowells@redhat.com>
In newsgroup: linux.dev.kernel
> 
> However, on i386, for example, you've actually got at least two different I/O
> access domains, and I don't know how they impinge upon each other (IN/OUT vs
> MOV).
> 

You do, but those aren't the ones.

What you have is instead MOVNT versus everything else.  IN/OUT are
total sledgehammers, as they imply not only nonposted operation, but
the instruction implies wait for completion; this is required since
IN/OUT support emulation via SMI.

	-hpa
-
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/