Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754448AbdGLVtX (ORCPT ); Wed, 12 Jul 2017 17:49:23 -0400 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:56505 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753410AbdGLVtW (ORCPT ); Wed, 12 Jul 2017 17:49:22 -0400 X-ME-Sender: X-Sasl-enc: pxP0MD1crT504/TwtIYa6GNfXcv+2zw3cPhaU1ulM0yF 1499896160 Date: Wed, 12 Jul 2017 14:49:20 -0700 From: Andres Freund To: Josh Poimboeuf Cc: x86@kernel.org, linux-kernel@vger.kernel.org, live-patching@vger.kernel.org, Linus Torvalds , Andy Lutomirski , Jiri Slaby , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra , Mike Galbraith Subject: Re: [PATCH v3 00/10] x86: ORC unwinder (previously undwarf) Message-ID: <20170712214920.5droainfqjmq7sgu@alap3.anarazel.de> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 551 Lines: 15 Hi, On 2017-07-11 10:33:37 -0500, Josh Poimboeuf wrote: > The simpler debuginfo format also enables the unwinder to be much faster > than DWARF, which is important for perf and lockdep. Is this going to be usable for userland call-graphs as well? If one converts dwarf to that, I mean? Because right now with perf dwarf is often the only thing that works properly through libc, as libc isn't compiled with fps and has hardcoded asm not preserving fp. lbr isn't available for many events, and often not at all available in VMs etc. Regards, Andres