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

[Xen-devel] Re: Linux questions



On 4/12/07 11:44, "Andi Kleen" <andi@xxxxxxxxxxxxxx> wrote:

>> I must disagree! And I *know* that RDTSC is not a serialising instruction...
>> 
>> If we race, then there was an interrupt. Interrupt delivery is a
>> serialisation point for the interrupted instruction stream.
> 
> The synchronization relies on the RDTSC happening between the
> two sequence number checks. Otherwise you can get inconsistent state
> between RDTSC and the xtime data which might be changing asynchronously
> on another CPU. Therefore you need RDTSC barriers.

Our monotonic_clock() implementation does not reference xtime nor its
seqlock. If it did, you would be correct.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.