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

[Xen-devel] Re: Linux questions

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
From: Andi Kleen <andi@xxxxxxxxxxxxxx>
Date: Tue, 4 Dec 2007 13:23:01 +0100
Cc: Andi Kleen <andi@xxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Jan Beulich <jbeulich@xxxxxxxxxx>, Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Delivery-date: Thu, 06 Dec 2007 08:34:16 -0800
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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

Well it applies to other state too. There certainly is a seqlock
equivalent. If you can guarantee the interrupt changing that is 
always on the same CPU that would be safe, otherwise not.

-Andi


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

References:
- [Xen-devel] Re: Linux questions
  - From: Andi Kleen
- [Xen-devel] Re: Linux questions
  - From: Keir Fraser

Prev by Date: [Xen-devel] Re: Linux questions
Next by Date: [Xen-devel] x86_32/entry.S question
Previous by thread: [Xen-devel] Re: Linux questions
Next by thread: [Xen-devel] [PATCH] [Xend/Xm/ACM] [2/2] Implement legacy XML-RPC interface for ACM commands
Index(es):
- Date
- Thread

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