From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: Linux questions Date: Tue, 04 Dec 2007 12:13:41 +0100 Message-ID: References: <475538A4.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: (Keir Fraser's message of "Tue\, 04 Dec 2007 10\:55\:15 +0000") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, Jan Beulich , Samuel Thibault List-Id: xen-devel@lists.xenproject.org Keir Fraser writes: > On 4/12/07 10:23, "Jan Beulich" wrote: > >> I have to disagree: At least the uses of barrier() in monotonic_clock() appear >> to be in places where in reality (and from a theoretical standpoint) rmb() >> ought to be used. > > We're sync'ing against concurrent updates of a this_cpu variable. We can > only race updates in a local ISR, and hence barrier() suffices. Not if you use RDTSC inside the loop. -Andi