From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Linux questions Date: Mon, 03 Dec 2007 11:40:28 +0000 Message-ID: <4753F93C.76E4.0078.0@novell.com> References: <4753F583.76E4.0078.0@novell.com> <20071203112958.GB4930@implementation.labri.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20071203112958.GB4930@implementation.labri.fr> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Samuel Thibault Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >>> Samuel Thibault 03.12.07 12:29 >>> >Jan Beulich, le Mon 03 Dec 2007 11:24:35 +0000, a =E9crit : >> 2) What is the reason for the inconsistent use of rmb() vs. barrier() = in >> time-xen.c? It would seem to me that rmb() should be sufficient in all >> cases. > >rmb() is more powerful than barrier(), not the converse. Oh, sorry, I mixed barrier() with mb(). So the proposal would then simply be the other way around (the use of locked operations or fence instructio= ns on x86 is really unnecessary as long as WC memory or non-temporal stores don't need to be taken into consideration). Jan