Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965083AbVKVSXd (ORCPT ); Tue, 22 Nov 2005 13:23:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965086AbVKVSXd (ORCPT ); Tue, 22 Nov 2005 13:23:33 -0500 Received: from ms-smtp-04.nyroc.rr.com ([24.24.2.58]:55727 "EHLO ms-smtp-04.nyroc.rr.com") by vger.kernel.org with ESMTP id S965083AbVKVSXc (ORCPT ); Tue, 22 Nov 2005 13:23:32 -0500 Date: Tue, 22 Nov 2005 13:22:57 -0500 (EST) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Christopher Friesen cc: Fernando Lopez-Lezcano , Ingo Molnar , linux-kernel@vger.kernel.org, "Paul E. McKenney" , "K.R. Foley" , Thomas Gleixner , pluto@agmk.net, john cooper , Benedikt Spranger , Daniel Walker , Tom Rini , George Anzinger Subject: Re: test time-warps [was: Re: 2.6.14-rt13] In-Reply-To: <43835D01.3020304@nortel.com> Message-ID: References: <20051115090827.GA20411@elte.hu> <1132608728.4805.20.camel@cmn3.stanford.edu> <20051121221511.GA7255@elte.hu> <20051121221941.GA11102@elte.hu> <20051122111623.GA948@elte.hu> <1132681766.21797.10.camel@cmn3.stanford.edu> <43835D01.3020304@nortel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1200 Lines: 33 On Tue, 22 Nov 2005, Christopher Friesen wrote: > Fernando Lopez-Lezcano wrote: > > >>Basically if there is an observable and provable warp in the TSC output > >>then it must not be used for any purpose that is not strictly > >>per-CPU-ified (such as userspace threads bound to a single CPU, and the > >>TSC never used between threads). > > > Apparently that's the case. > > What about periodically re-syncing the TSCs on the cpus? Are they > writeable? > I believe you can reset them to zero, but I don't think you can set them to anything else. I had to do something similar a few years ago, and I don't have the specs in front of me, so this is coming straight from memory. Even if you could reset them, it would be very difficult to make all CPUs have the same counter. Not to mention that this would also screw up all timings elsewhere when the sync happens. Remember, this would have to work not just on 2 cpus, but 4, 8 and beyond. -- Steve - 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/