From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755261AbYIWVC0 (ORCPT ); Tue, 23 Sep 2008 17:02:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752202AbYIWVCS (ORCPT ); Tue, 23 Sep 2008 17:02:18 -0400 Received: from smtp-out.google.com ([216.239.33.17]:48165 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751359AbYIWVCR (ORCPT ); Tue, 23 Sep 2008 17:02:17 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=message-id:date:from:to:subject:cc:in-reply-to: mime-version:content-type:content-transfer-encoding: content-disposition:references:x-gmailtapped-by; b=jelKqt6mZ44uJoTO6VVbDtiL+vfHJmx/UsZzjDDlV9vHKCJ4KkHG9wb04xZXduFG7 kPGHFQFxfWt6qwLnCBQJA== Message-ID: <33307c790809231402o24c93820tcfbf80d116c729c3@mail.gmail.com> Date: Tue, 23 Sep 2008 14:02:08 -0700 From: "Martin Bligh" To: "Thomas Gleixner" Subject: Re: Unified tracing buffer Cc: "Masami Hiramatsu" , "Linus Torvalds" , "Mathieu Desnoyers" , "Linux Kernel Mailing List" , "Steven Rostedt" , darren@dvhart.com, "Frank Ch. Eigler" , systemtap-ml In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <33307c790809191433w246c0283l55a57c196664ce77@mail.gmail.com> <48D921B3.2060809@redhat.com> <48D93CAF.8070000@redhat.com> <33307c790809231238m1e80fef4rce8a80722ff245f1@mail.gmail.com> <33307c790809231250y298ede7cqbee5a613ed6dbad5@mail.gmail.com> X-GMailtapped-By: 172.24.198.93 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >> I think the tolerance is about 500 cycles. If that's not sufficient, I guess >> we'll have to either live with some slight misordering (which people have >> pointed out is kind of inevitable anyway) on these broken machines? >> It was sufficient for what we were using it for, but maybe not for everyone. > > Well, I dont care about the trace reordering at all. I care about user > space visible time going backwards issues observed via the > gettimeofday vsyscall. 500 cycles should be fine, I doubt that we can > migrate in less than that :) Right, that's what we were interested in. > I guess you try this only for machines where the TSC runs with > constant frequency, right ? We don't do DVFS on the 'broken' TSC machines, just halt. But yes, it's selective