Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754466Ab0DSLLA (ORCPT ); Mon, 19 Apr 2010 07:11:00 -0400 Received: from mx1.redhat.com ([209.132.183.28]:2186 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754421Ab0DSLK6 (ORCPT ); Mon, 19 Apr 2010 07:10:58 -0400 Message-ID: <4BCC3A3E.9070909@redhat.com> Date: Mon, 19 Apr 2010 14:10:54 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.0.4-1.fc12 Thunderbird/3.0.4 MIME-Version: 1.0 To: Peter Zijlstra CC: Jeremy Fitzhardinge , Glauber Costa , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Marcelo Tosatti , Zachary Amsden Subject: Re: [PATCH 1/5] Add a global synchronization point for pvclock References: <1271356648-5108-1-git-send-email-glommer@redhat.com> <1271356648-5108-2-git-send-email-glommer@redhat.com> <4BC8CA52.4090703@goop.org> <1271673545.1674.743.camel@laptop> <4BCC3584.1050501@redhat.com> <1271675100.1674.818.camel@laptop> In-Reply-To: <1271675100.1674.818.camel@laptop> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 843 Lines: 33 On 04/19/2010 02:05 PM, Peter Zijlstra wrote: >> >>> ACCESS_ONCE() is your friend. >>> >>> >> I think it's implied with atomic64_read(). >> > Yes it would be. I was merely trying to point out that > > last = ACCESS_ONCE(last_value); > > Is a narrower way of writing: > > last = last_value; > barrier(); > > In that it need not clobber all memory locations and makes it instantly > clear what we want the barrier for. > Oh yes, just trying to avoid a patch with both atomic64_read() and ACCESS_ONCE(). -- error compiling committee.c: too many arguments to function -- 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/