From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Michael Petlan <mpetlan@redhat.com>,
Ian Rogers <irogers@google.com>,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 1/9] perf tools: Add build id shell test
Date: Tue, 13 Oct 2020 21:15:09 +0200 [thread overview]
Message-ID: <20201013191509.GA1199570@krava> (raw)
In-Reply-To: <20201013161340.GH1063281@kernel.org>
On Tue, Oct 13, 2020 at 01:13:40PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Wed, Sep 30, 2020 at 07:15:04PM +0200, Jiri Olsa escreveu:
> > Adding test for build id cache that adds binary
> > with sha1 and md5 build ids and verifies it's
> > added properly.
> >
> > The test updates build id cache with perf record
> > and perf buildid-cache -a.
>
>
> [root@five ~]# perf test "build id"
> 82: build id cache operations : Skip
> [root@five ~]# set -o vi
> [root@five ~]# perf test -v "build id"
> 82: build id cache operations :
> --- start ---
> test child forked, pid 88384
> failed: no test binaries
> test child finished with -2
> ---- end ----
> build id cache operations: Skip
> [root@five ~]#
hm, output looks like older version of the test
>
> Also the other patches clashed with Namhyung's patch series, can you
> please check?
right, new api is different now
>
> I've just pushed what I have to acme/perf/core
I rebased and pushed perf/build_id_size branch, also will post new version
thanks,
jirka
next prev parent reply other threads:[~2020-10-13 19:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 17:15 [PATCH 0/9] perf tools: Add support for build id with different sizes Jiri Olsa
2020-09-30 17:15 ` [PATCH 1/9] perf tools: Add build id shell test Jiri Olsa
2020-10-01 2:00 ` Ian Rogers
2020-10-01 9:25 ` Jiri Olsa
2020-10-01 10:25 ` Jiri Olsa
2020-10-01 16:58 ` Ian Rogers
2020-10-01 19:05 ` [PATCHv2 " Jiri Olsa
2020-10-02 13:07 ` Namhyung Kim
2020-10-02 17:34 ` Ian Rogers
2020-10-02 19:29 ` Jiri Olsa
2020-10-06 1:37 ` Namhyung Kim
2020-10-08 9:11 ` Jiri Olsa
2020-10-08 15:22 ` Ian Rogers
2020-10-02 20:55 ` Arnaldo Carvalho de Melo
2020-10-05 15:58 ` [PATCHv3 " Jiri Olsa
2020-10-13 16:13 ` [PATCH " Arnaldo Carvalho de Melo
2020-10-13 19:15 ` Jiri Olsa [this message]
2020-09-30 17:15 ` [PATCH 2/9] perf tools: Use build_id object in dso Jiri Olsa
2020-10-01 2:01 ` Ian Rogers
2020-09-30 17:15 ` [PATCH 3/9] perf tools: Pass build_id object to filename__read_build_id Jiri Olsa
2020-10-01 5:17 ` Ian Rogers
2020-09-30 17:15 ` [PATCH 4/9] perf tools: Pass build id object to sysfs__read_build_id Jiri Olsa
2020-10-01 5:20 ` Ian Rogers
2020-09-30 17:15 ` [PATCH 5/9] perf tools: Pass build_id object to build_id__sprintf Jiri Olsa
2020-10-01 5:24 ` Ian Rogers
2020-09-30 17:15 ` [PATCH 6/9] perf tools: Pass build_id object to dso__set_build_id Jiri Olsa
2020-10-01 5:25 ` Ian Rogers
2020-09-30 17:15 ` [PATCH 7/9] perf tools: Pass build_id object to dso__build_id_equal Jiri Olsa
2020-10-01 5:25 ` Ian Rogers
2020-09-30 17:15 ` [PATCH 8/9] perf tools: Add size to struct perf_record_header_build_id Jiri Olsa
2020-10-01 5:31 ` Ian Rogers
2020-09-30 17:15 ` [PATCH 9/9] perf tools: Align buildid list output for short build ids Jiri Olsa
2020-10-01 5:35 ` Ian Rogers
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=20201013191509.GA1199570@krava \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--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.