All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: He Kuang <hekuang@huawei.com>,
	Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@kernel.org>, David Ahern <dsahern@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: [PATCH] perf unwind: Limit warnings when asked for not supported unwind
Date: Mon, 19 Jun 2017 23:28:43 +0200	[thread overview]
Message-ID: <20170619212843.GC19183@krava> (raw)
In-Reply-To: <CA+JHD91HyFiNkRpJU+y1ppQO6t8KS3QQKEacNw_bu6s9PFH11w@mail.gmail.com>

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" <jolsa@redhat.com> 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

      parent reply	other threads:[~2017-06-19 21:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-16 12:12 [PATCH] perf unwind: Limit warnings when asked for not supported unwind Jiri Olsa
2017-06-16 16:25 ` Arnaldo Carvalho de Melo
2017-06-18 22:53   ` Jiri Olsa
     [not found]     ` <CA+JHD91HyFiNkRpJU+y1ppQO6t8KS3QQKEacNw_bu6s9PFH11w@mail.gmail.com>
2017-06-19 21:28       ` Jiri Olsa [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170619212843.GC19183@krava \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=arnaldo.melo@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=hekuang@huawei.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.