From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andi Kleen <andi@firstfloor.org>
Subject: Re: Linux questions
Date: Tue, 4 Dec 2007 13:23:01 +0100
Message-ID: <20071204122301.GC10287@one.firstfloor.org>
References: <20071204114405.GB10287@one.firstfloor.org>
	<C37AF103.195D4%Keir.Fraser@cl.cam.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
In-Reply-To: <C37AF103.195D4%Keir.Fraser@cl.cam.ac.uk>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Andi Kleen <andi@firstfloor.org>, xen-devel@lists.xensource.com, Jan Beulich <jbeulich@novell.com>, Samuel Thibault <samuel.thibault@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

> 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