From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Wang Nan <wangnan0@huawei.com>
Subject: Re: [PATCH 1/2] perf evsel: Fix probing of precise_ip level for default cycles event
Date: Wed, 14 Jun 2017 07:57:41 -0300 [thread overview]
Message-ID: <20170614105740.GB32020@kernel.org> (raw)
In-Reply-To: <20170614105154.lg5prmc2xfwivjfz@gmail.com>
Em Wed, Jun 14, 2017 at 12:51:55PM +0200, Ingo Molnar escreveu:
>
> * Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
>
> > Can you try with the patch below, which is hackish but the minimal fix at this
> > point. Later I'll come up with a way of returning a fully configured cycles
> > evsel, which will make the tools code simpler, moving more stuff to the
> > libraries.
>
> Yeah, this patch on top of your tree seems to work better now.
So how do we proceed, do you want to keep these two as separate or can I
squash them together, fix that problem with the unwind library and
provide a new perf/urgent for you to use?
Off to breakfast now tho :-)
- Arnaldo
next prev parent reply other threads:[~2017-06-14 10:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 23:23 [GIT PULL 0/2] perf/urgent fixes for 4.12 Arnaldo Carvalho de Melo
2017-06-13 23:23 ` [PATCH 1/2] perf evsel: Fix probing of precise_ip level for default cycles event Arnaldo Carvalho de Melo
2017-06-14 5:45 ` Ingo Molnar
2017-06-14 10:44 ` Arnaldo Carvalho de Melo
2017-06-14 10:51 ` Ingo Molnar
2017-06-14 10:57 ` Arnaldo Carvalho de Melo [this message]
2017-06-14 13:55 ` Ingo Molnar
2017-06-14 14:44 ` Arnaldo Carvalho de Melo
2017-06-14 13:29 ` Arnaldo Carvalho de Melo
2017-06-14 13:52 ` perf: unwind: target platform=x86 not supported was: " Arnaldo Carvalho de Melo
2017-06-14 14:19 ` Jiri Olsa
2017-06-14 14:31 ` Jiri Olsa
2017-06-14 14:47 ` Arnaldo Carvalho de Melo
2017-06-14 14:06 ` Ingo Molnar
2017-06-14 14:46 ` Arnaldo Carvalho de Melo
2017-06-14 19:12 ` Arnaldo Carvalho de Melo
2017-06-13 23:23 ` [PATCH 2/2] perf tools: Fix build with ARCH=x86_64 Arnaldo Carvalho de Melo
2017-06-14 5:33 ` [GIT PULL 0/2] perf/urgent fixes for 4.12 Ingo Molnar
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=20170614105740.GB32020@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox