From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753951Ab1KHMRL (ORCPT ); Tue, 8 Nov 2011 07:17:11 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:47821 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751632Ab1KHMRJ (ORCPT ); Tue, 8 Nov 2011 07:17:09 -0500 Date: Tue, 8 Nov 2011 13:15:01 +0100 From: Ingo Molnar To: Pekka Enberg Cc: "Frank Ch. Eigler" , "Ted Ts'o" , Vince Weaver , Pekka Enberg , Anthony Liguori , Avi Kivity , "kvm@vger.kernel.org list" , "linux-kernel@vger.kernel.org List" , qemu-devel Developers , Alexander Graf , Blue Swirl , =?iso-8859-1?Q?Am=E9rico?= Wang , Linus Torvalds , Peter Zijlstra , Arnaldo Carvalho de Melo Subject: Re: [F.A.Q.] perf ABI backwards and forwards compatibility Message-ID: <20111108121501.GA1022@elte.hu> References: <20111106231953.GD4500@thunk.org> <20111107175942.GA9395@elte.hu> <20111107203514.GG24234@thunk.org> <20111108102235.GA1241@elte.hu> <20111108113150.GA13195@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=AWL,BAYES_00 autolearn=no SpamAssassin version=3.3.1 -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] 0.0 AWL AWL: From: address is in the auto white-list Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Pekka Enberg wrote: > [...] There's an easy fix for this too: improve "perf test" to > cover the cases you're intested in. While ABI spec would be a nice > addition, it's not going to make compatibility problems magically > go away. Yes, exactly - 'perf test' has been written with that exact purpose. In practice 'perf' will cover almost all parts of the ABI. The one notable thing that isnt being tested in a natural way is the 'group of events' abstraction - which, ironically, has been added on the perfmon guys' insistence. No app beyond the PAPI self-test makes actual use of it though, which results in an obvious lack of testing. Vince: the code is in tools/perf/builtin-test.c and our offer still stands, feel free to extend it. Maybe there's some other volunteer willing to do that? Thanks, Ingo