From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Zijlstra Subject: Re: [PATCH 1/5] Add a global synchronization point for pvclock Date: Mon, 19 Apr 2010 12:39:05 +0200 Message-ID: <1271673545.1674.743.camel@laptop> References: <1271356648-5108-1-git-send-email-glommer@redhat.com> <1271356648-5108-2-git-send-email-glommer@redhat.com> <4BC8CA52.4090703@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Glauber Costa , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, avi@redhat.com, Marcelo Tosatti , Zachary Amsden To: Jeremy Fitzhardinge Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:39956 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753096Ab0DSKjJ (ORCPT ); Mon, 19 Apr 2010 06:39:09 -0400 Received: from f199130.upc-f.chello.nl ([80.56.199.130] helo=dyad.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.69 #1 (Red Hat Linux)) id 1O3oNh-0006ZC-6d for kvm@vger.kernel.org; Mon, 19 Apr 2010 10:39:09 +0000 In-Reply-To: <4BC8CA52.4090703@goop.org> Sender: kvm-owner@vger.kernel.org List-ID: On Fri, 2010-04-16 at 13:36 -0700, Jeremy Fitzhardinge wrote: > > + do { > > + last = last_value; > > > Does this need a barrier() to prevent the compiler from re-reading > last_value for the subsequent lines? Otherwise "(ret < last)" and > "return last" could execute with different values for "last". > ACCESS_ONCE() is your friend.