Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760411AbXFFOPt (ORCPT ); Wed, 6 Jun 2007 10:15:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751124AbXFFOPm (ORCPT ); Wed, 6 Jun 2007 10:15:42 -0400 Received: from gw.goop.org ([64.81.55.164]:33816 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750906AbXFFOPl (ORCPT ); Wed, 6 Jun 2007 10:15:41 -0400 Message-ID: <4666C183.9060008@goop.org> Date: Wed, 06 Jun 2007 07:15:31 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: Andi Kleen CC: Jan Beulich , Ingo Molnar , Thomas Gleixner , Andrew Morton , Linus Torvalds , virtualization@lists.osdl.org, Xen-devel , Chris Wright , lkml , Jiri Bohac Subject: Re: [Xen-devel] [patch 14/33] xen: xen time implementation References: <20070522140941.802382212@goop.org> <46668EC6.76E4.0078.0@novell.com> <466686E2.4040004@goop.org> <200706061226.11326.ak@suse.de> In-Reply-To: <200706061226.11326.ak@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 701 Lines: 19 Andi Kleen wrote: >> I once had some code in there to do that, implemented in very boneheaded >> way with a spinlock to protect the "last time returned" variable. I >> expect there's a better way to implement it. >> > > But any per CPU setup likely needs this to avoid non monotonicity Yeah. The point I didn't quite make was that this should be something that the clock core should handle rather than dealing with it in every clocksource. J - 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/