From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, Michael Petlan <mpetlan@redhat.com>,
Jiri Olsa <jolsa@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [PATCH 01/10] perf buildid-list: Show running kernel build id fix
Date: Fri, 27 Nov 2015 22:22:22 -0300 [thread overview]
Message-ID: <1448673751-20949-2-git-send-email-acme@kernel.org> (raw)
In-Reply-To: <1448673751-20949-1-git-send-email-acme@kernel.org>
From: Michael Petlan <mpetlan@redhat.com>
The --kernel option of perf buildid-list tool should show the running
kernel buildid. The functionality has been lost during other changes of
the related code.
The build_id__sprintf() function should return length of the build-id
string, but it was the length of the build-id raw data instead. Due to
that, some return value checking caused that the final string was not
printed out.
With this patch the build_id__sprintf() returns the correct value, so
the --kernel option works again.
Before:
# perf buildid-list --kernel
#
After:
# perf buildid-list --kernel
972c1edab5bdc06cc224af45d510af662a3c6972
#
Signed-off-by: Michael Petlan <mpetlan@redhat.com>
Cc: Jiri Olsa <jolsa@redhat.com>
Cc: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
LPU-Reference: 1448632089.24573.114.camel@redhat.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
---
tools/perf/util/build-id.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/util/build-id.c b/tools/perf/util/build-id.c
index 217b5a60e2ab..6a7e273a514a 100644
--- a/tools/perf/util/build-id.c
+++ b/tools/perf/util/build-id.c
@@ -91,7 +91,7 @@ int build_id__sprintf(const u8 *build_id, int len, char *bf)
bid += 2;
}
- return raw - build_id;
+ return (bid - bf) + 1;
}
int sysfs__sprintf_build_id(const char *root_dir, char *sbuild_id)
--
2.1.0
next prev parent reply other threads:[~2015-11-28 1:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-28 1:22 [GIT PULL 00/10] perf/core improvements and fixes Arnaldo Carvalho de Melo
2015-11-28 1:22 ` Arnaldo Carvalho de Melo [this message]
2015-11-28 1:22 ` [PATCH 02/10] perf test: 'unwind' test should create kernel maps Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 03/10] perf list: Add support for PERF_COUNT_SW_BPF_OUT Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 04/10] perf list: Robustify event printing routine Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 05/10] perf report: Show error message when processing sample fails Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 06/10] perf hists: Do not skip elided fields when processing samples Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 07/10] perf hists browser: Update nr entries regardless of min percent Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 08/10] tools lib bpf: Collect map definition in bpf_object Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 09/10] tools lib bpf: Extract and collect map names from BPF object file Arnaldo Carvalho de Melo
2015-11-28 1:22 ` [PATCH 10/10] perf bpf: Rename bpf config to program config Arnaldo Carvalho de Melo
2015-11-28 9:50 ` [GIT PULL 00/10] perf/core improvements and fixes Ingo Molnar
2015-11-29 13:16 ` Namhyung Kim
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=1448673751-20949-2-git-send-email-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.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;
as well as URLs for NNTP newsgroup(s).