From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754546AbYIYVD0 (ORCPT ); Thu, 25 Sep 2008 17:03:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754175AbYIYVC4 (ORCPT ); Thu, 25 Sep 2008 17:02:56 -0400 Received: from gw.goop.org ([64.81.55.164]:46343 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753822AbYIYVCz (ORCPT ); Thu, 25 Sep 2008 17:02:55 -0400 Message-ID: <48DBFC7D.4050208@goop.org> Date: Thu, 25 Sep 2008 14:02:53 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: Linus Torvalds CC: Ingo Molnar , Martin Bligh , Peter Zijlstra , Martin Bligh , Steven Rostedt , linux-kernel@vger.kernel.org, Thomas Gleixner , Andrew Morton , prasad@linux.vnet.ibm.com, Mathieu Desnoyers , "Frank Ch. Eigler" , David Wilder , hch@lst.de, Tom Zanussi , Steven Rostedt Subject: Re: [RFC PATCH 1/3] Unified trace buffer References: <33307c790809241403w236f2242y18ba44982d962287@mail.gmail.com> <1222339303.16700.197.camel@lappy.programming.kicks-ass.net> <8f3aa8d60809250733q70561e6agfa3b00da83773e9f@mail.gmail.com> <1222354409.16700.215.camel@lappy.programming.kicks-ass.net> <33307c790809250825u567d3680w682899c111e10ed6@mail.gmail.com> <20080925153635.GA12840@elte.hu> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Linus Torvalds wrote: > As for C2/C3 - that's just an argument for *not* doing anything at trace > time. What do you think happens when you try to trace through those > things? You're much better off trying to sort out the problems later, when > you don't hold critical locks and are possibly deep down in some buggy > ACPI code, and you're trying to trace it exactly _because_ it is buggy. > That suggests that frequency changes should be recorded at a lower layer as well, along with full timestamps and deltas, so that a log parser can correctly generate the timestamps without having to parse higher-level trace records. Maybe the simplest thing to do is make the full timestamp records also include frequency and offset information (to deal with discontinuities caused by things like a vcpu switching between physical cpus with unsynced tscs). J