From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33440) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNkc3-00035v-5W for qemu-devel@nongnu.org; Tue, 08 Nov 2011 07:17:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RNkbx-00024Z-C6 for qemu-devel@nongnu.org; Tue, 08 Nov 2011 07:17:11 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:58304) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RNkbx-00024T-67 for qemu-devel@nongnu.org; Tue, 08 Nov 2011 07:17:05 -0500 Date: Tue, 8 Nov 2011 13:15:01 +0100 From: Ingo Molnar 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: Subject: Re: [Qemu-devel] [F.A.Q.] perf ABI backwards and forwards compatibility List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Pekka Enberg Cc: Alexander Graf , Ted Ts'o , Peter Zijlstra , "kvm@vger.kernel.org list" , qemu-devel Developers , Vince Weaver , "linux-kernel@vger.kernel.org List" , Pekka Enberg , Blue Swirl , "Frank Ch. Eigler" , Arnaldo Carvalho de Melo , Avi Kivity , =?iso-8859-1?Q?Am=E9rico?= Wang , Linus Torvalds * 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