From: Jiri Olsa <jolsa@redhat.com>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH v2 2/3] lib kallsyms: parse using io api
Date: Tue, 5 May 2020 16:25:21 +0200 [thread overview]
Message-ID: <20200505142521.GD2041406@krava> (raw)
In-Reply-To: <20200501221315.54715-3-irogers@google.com>
On Fri, May 01, 2020 at 03:13:14PM -0700, Ian Rogers wrote:
SNIP
> diff --git a/tools/lib/symbol/kallsyms.c b/tools/lib/symbol/kallsyms.c
> index 1a7a9f877095..e335ac2b9e19 100644
> --- a/tools/lib/symbol/kallsyms.c
> +++ b/tools/lib/symbol/kallsyms.c
> @@ -1,7 +1,9 @@
> // SPDX-License-Identifier: GPL-2.0
> #include "symbol/kallsyms.h"
> +#include "api/io.h"
> #include <stdio.h>
> -#include <stdlib.h>
> +#include <sys/stat.h>
> +#include <fcntl.h>
>
> u8 kallsyms2elf_type(char type)
> {
> @@ -15,74 +17,62 @@ bool kallsyms__is_function(char symbol_type)
> return symbol_type == 'T' || symbol_type == 'W';
> }
>
> -/*
> - * While we find nice hex chars, build a long_val.
> - * Return number of chars processed.
> - */
> -int hex2u64(const char *ptr, u64 *long_val)
hi,
when you remove in here hex2u64, you'll break the compile:
LINK perf
/usr/bin/ld: perf-in.o: in function `modules__parse':
/home/jolsa/linux-perf/tools/perf/util/symbol.c:607: undefined reference to `hex2u64'
/usr/bin/ld: /home/jolsa/linux-perf/tools/perf/util/symbol.c:607: undefined reference to `hex2u64'
/usr/bin/ld: perf-in.o: in function `dso__load_perf_map':
/home/jolsa/linux-perf/tools/perf/util/symbol.c:1477: undefined reference to `hex2u64'
/usr/bin/ld: /home/jolsa/linux-perf/tools/perf/util/symbol.c:1483: undefined reference to `hex2u64'
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile.perf:629: perf] Error 1
make[1]: *** [Makefile.perf:225: sub-make] Error 2
make: *** [Makefile:70: all] Error 2
that hex2u64 move needs to come before this change
jirka
next prev parent reply other threads:[~2020-05-05 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 22:13 [PATCH v2 0/3] Improvements for kallsyms__parse Ian Rogers
2020-05-01 22:13 ` [PATCH v2 1/3] perf bench: add kallsyms parsing Ian Rogers
2020-05-08 13:04 ` [tip: perf/core] perf bench: Add " tip-bot2 for Ian Rogers
2020-05-01 22:13 ` [PATCH v2 2/3] lib kallsyms: parse using io api Ian Rogers
2020-05-05 12:37 ` Arnaldo Carvalho de Melo
2020-05-05 14:25 ` Jiri Olsa [this message]
2020-05-05 14:37 ` Ian Rogers
2020-05-05 16:13 ` Arnaldo Carvalho de Melo
2020-05-08 13:04 ` [tip: perf/core] libsymbols kallsyms: Parse " tip-bot2 for Ian Rogers
2020-05-01 22:13 ` [PATCH v2 3/3] lib kallsyms: move hex2u64 out of header Ian Rogers
2020-05-08 13:04 ` [tip: perf/core] libsymbols kallsyms: Move " tip-bot2 for Ian Rogers
2020-05-05 12:38 ` [PATCH v2 0/3] Improvements for kallsyms__parse Arnaldo Carvalho de Melo
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=20200505142521.GD2041406@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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