Re: [PATCH 1/5] Add a global synchronization point for pvclock

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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 kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux