Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933083Ab2EPTge (ORCPT ); Wed, 16 May 2012 15:36:34 -0400 Received: from mga02.intel.com ([134.134.136.20]:64566 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760543Ab2EPTgb (ORCPT ); Wed, 16 May 2012 15:36:31 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,351,1309762800"; d="scan'208";a="144838873" Message-ID: <4FB401B2.1010906@linux.intel.com> Date: Wed, 16 May 2012 12:36:18 -0700 From: Arjan van de Ven User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 To: Linus Torvalds CC: Steven Rostedt , LKML , Ingo Molnar , Frederic Weisbecker , David Sharp , Vaibhav Nagarnaik , Peter Zijlstra , Andrew Morton Subject: Re: [RFC][PATCH] tracing: Remove useless 4 bytes of padding from every event References: <1337175871.6724.46.camel@gandalf.stny.rr.com> In-Reply-To: X-Enigmail-Version: 1.4.1 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 Content-Length: 955 Lines: 26 On 5/16/2012 12:33 PM, Linus Torvalds wrote: > On Wed, May 16, 2012 at 6:44 AM, Steven Rostedt wrote: >> >> But this change will break PowerTop v1. Thus my question is, how long do >> we need to keep this wasted space in the ring buffers to satisfy an out >> of date tool? > > The wasted space seems of limited importance. > > More important is to check which distros have the new powertop. > > F16 and F17 seem to have powertop-1.98, which I assume is the new > world order already. But maybe I assume incorrectly. this is the one that will break > > F14 (which I personally still use, since it doesn't have gnome3) is 1.13. this one is fine, it does not use perf events at all. -- 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/