From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Kemeng Shi <shikemeng@huawei.com>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
peterz@infradead.org, mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, ndesaulniers@google.com, irogers@google.com,
tmricht@linux.ibm.com, hushiyuan@huawei.com,
hewenliang4@huawei.com
Subject: Re: [PATCH] perf report: Fix arm64 gap between kernel start and module end
Date: Mon, 30 Mar 2020 10:11:29 -0300 [thread overview]
Message-ID: <20200330131129.GB31702@kernel.org> (raw)
In-Reply-To: <33fd24c4-0d5a-9d93-9b62-dffa97c992ca@huawei.com>
Em Mon, Mar 30, 2020 at 03:41:11PM +0800, Kemeng Shi escreveu:
> diff --git a/tools/perf/arch/arm64/util/Build b/tools/perf/arch/arm64/util/Build
> index 393b9895c..37cbfa5e9 100644
> --- a/tools/perf/arch/arm64/util/Build
> +++ b/tools/perf/arch/arm64/util/Build
> @@ -2,6 +2,7 @@ libperf-y += header.o
> libperf-y += tsc.o
> libperf-y += sym-handling.o
> libperf-y += kvm-stat.o
> +libperf-y += machine.o
You made the patch against an old perf codebase, right? This libperf-y
above was changed to perf-y here:
commit 5ff328836dfde0cef9f28c8b8791a90a36d7a183
Author: Jiri Olsa <jolsa@kernel.org>
Date: Wed Feb 13 13:32:39 2019 +0100
perf tools: Rename build libperf to perf
----
I'm fixing this up, please check my perf/core branch later to see that
all is working as intended.
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/core
Thanks,
- Arnaldo
next prev parent reply other threads:[~2020-03-30 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-30 7:41 [PATCH] perf report: Fix arm64 gap between kernel start and module end Kemeng Shi
2020-03-30 13:11 ` Arnaldo Carvalho de Melo [this message]
2020-03-30 13:18 ` Arnaldo Carvalho de Melo
2020-04-02 13:41 ` [PATCH 0/1] perf tools: fix compilation on Arm James Clark
2020-04-02 13:41 ` [PATCH 1/1] " James Clark
2021-02-09 12:40 ` [PATCH] perf report: Fix arm64 gap between kernel start and module end Arnaldo Carvalho de Melo
2021-02-09 12:46 ` Arnaldo Carvalho de Melo
2020-03-31 4:13 ` Kemeng Shi
2020-04-04 8:41 ` [tip: perf/urgent] perf symbols: " tip-bot2 for Kemeng Shi
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=20200330131129.GB31702@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=hewenliang4@huawei.com \
--cc=hushiyuan@huawei.com \
--cc=irogers@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=shikemeng@huawei.com \
--cc=tmricht@linux.ibm.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).