From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24679 invoked by alias); 16 Aug 2007 16:17:59 -0000 Received: (qmail 23173 invoked by uid 48); 16 Aug 2007 16:17:49 -0000 Date: Thu, 16 Aug 2007 18:17:00 -0000 Message-ID: <20070816161749.23171.qmail@sourceware.org> From: "joshua dot i dot stone at intel dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070124160955.3916.fche@redhat.com> References: <20070124160955.3916.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/3916] improve timing monotony X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q3/txt/msg00354.txt.bz2 ------- Additional Comments From joshua dot i dot stone at intel dot com 2007-08-16 16:17 ------- (In reply to comment #5) > However, I think this still needs to be discussed (especially, > about Core/Core2 architecture and newer AMD processors). There is a synthesized cpu feature flag X86_FEATURE_CONSTANT_TSC, added in 2.6.13 for x86_64 and 2.6.16 for i386. Further, in 2.6.18 there's a tsc_khz variable as a companion to the cpu_khz, and a check_tsc_unstable(). So hopefully we can make use of these features, though we'll need to gate it with autoconf to continue supporting older kernels. -- http://sourceware.org/bugzilla/show_bug.cgi?id=3916 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.