Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750802AbbEXGUt (ORCPT ); Sun, 24 May 2015 02:20:49 -0400 Received: from mail-wg0-f47.google.com ([74.125.82.47]:35123 "EHLO mail-wg0-f47.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750707AbbEXGUs (ORCPT ); Sun, 24 May 2015 02:20:48 -0400 Date: Sun, 24 May 2015 08:20:43 +0200 From: Ingo Molnar To: Thomas Gleixner Cc: John Stultz , LKML , Badhri Jagan Sridharan Subject: Re: [PATCH 4/7] tracing: timer: Add deferrable flag to timer_start Message-ID: <20150524062043.GA13305@gmail.com> References: <1432142376-2077-1-git-send-email-john.stultz@linaro.org> <1432142376-2077-5-git-send-email-john.stultz@linaro.org> <20150521061837.GB11077@gmail.com> <20150523081731.GA5428@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150523081731.GA5428@gmail.com> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 930 Lines: 26 * Ingo Molnar wrote: > > [...] So the field size is available for the tool. If the tool > > blindly applies the format string, it's hardly a fault of the > > kernel. And there is no point to bloat 32bit tracing with 64bit > > entries just because some random tool might be stupid. > > Yeah, in a perfect world and so we could define arbitrarily complex > interfaces and expect tooling to follow it. OTOH, on a second thought, libtraceevent handles this correctly, so the chance for tooling to get this wrong is much smaller than for other ABIs. Plus the advantages on 32-bit systems you mentioned are real as well - so I concur with you. Thanks, Ingo -- 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/