[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111108113150.GA13195@redhat.com>
Date: Tue, 8 Nov 2011 06:31:50 -0500
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: "Ted Ts'o" <tytso@....edu>, Pekka Enberg <penberg@...helsinki.fi>,
Vince Weaver <vince@...ter.net>,
Pekka Enberg <penberg@...nel.org>,
Anthony Liguori <anthony@...emonkey.ws>,
Avi Kivity <avi@...hat.com>,
"kvm@...r.kernel.org list" <kvm@...r.kernel.org>,
"linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>,
qemu-devel Developers <qemu-devel@...gnu.org>,
Alexander Graf <agraf@...e.de>,
Blue Swirl <blauwirbel@...il.com>,
Américo Wang <xiyou.wangcong@...il.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [F.A.Q.] perf ABI backwards and forwards compatibility
Hi -
On Tue, Nov 08, 2011 at 11:22:35AM +0100, Ingo Molnar wrote:
> [...] These examples show *PICTURE PERFECT* forwards ABI
> compatibility, using the ancient perf tool on a bleeding edge
> kernel. [...]
Almost: they demonstrate that those parts of the ABI that these
particular perf commands rely on have been impressively compatible.
Do you have any sort of ABI coverage measurement, to see what
parts of the ABI these perf commands do not use?
- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists