From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752283AbdFSV2x (ORCPT ); Mon, 19 Jun 2017 17:28:53 -0400 Received: from mx1.redhat.com ([209.132.183.28]:58558 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751022AbdFSV2w (ORCPT ); Mon, 19 Jun 2017 17:28:52 -0400 DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 1C47F80460 Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=jolsa@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 1C47F80460 Date: Mon, 19 Jun 2017 23:28:43 +0200 From: Jiri Olsa To: He Kuang , Arnaldo Carvalho de Melo Cc: Namhyung Kim , Jiri Olsa , Peter Zijlstra , Ingo Molnar , David Ahern , lkml , Arnaldo Carvalho de Melo Subject: Re: [PATCH] perf unwind: Limit warnings when asked for not supported unwind Message-ID: <20170619212843.GC19183@krava> References: <20170616121253.3816-1-jolsa@kernel.org> <20170616162504.GJ3645@kernel.org> <20170618225308.GC13111@krava> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.0 (2017-02-23) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Mon, 19 Jun 2017 21:28:51 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Jun 18, 2017 at 08:01:38PM -0300, Arnaldo Carvalho de Melo wrote: > Thanks! > > On Jun 18, 2017 7:53 PM, "Jiri Olsa" wrote: > > > On Fri, Jun 16, 2017 at 01:25:04PM -0300, Arnaldo Carvalho de Melo wrote: > > > Em Fri, Jun 16, 2017 at 02:12:53PM +0200, Jiri Olsa escreveu: > > > > Ingo reported following warning flooding the report out: > > > > > > > > unwind: target platform=x86 is not supported > > > > > > > > We trigger this warning when the dwarf unwinder is asked to > > > > process architecture which wasn't compiled in, like when you > > > > get 32bit application samples on your 64bit server and you > > > > don't have the 32bit remote unwind support compiled in. > > > > > > > > This patch limits the warning to single message for arch, > > > > and adds bits info. Above message is changed to: > > > > > > > > unwind: target platform=x86 32bit is not supported > > > > > > Can we have a more informative message telling the user what is > > > necessary to have this feature supported? > > > > > > The way you phrased it looks like it is not supported at all, while what > > > I read in the discussion is that one needs to have specific versions of > > > support libraries installed to have this working, right? > > > > exactly, I'll dig out from changelogs needed libunwind version > > and change the changelog in v2 He Kuang, could you please give me details on how to enable x86 remote unwind on x86_64 server? can't find that in the libunwind's ./configure script the feature tool detection example needs libunwind-x86.h header and -lunwind-x86.. which is provided by libunwind-devel.i686 pkg, but it conflicts with x86_64 libunwind-devel on fedora: Error: Transaction check error: file /usr/include/libunwind.h from install of libunwind-devel-1.2-1.fc25.i686 conflicts with file from package libunwind-devel-1.2-1.fc25.x86_64 jirka