From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Hulk Robot <hulkci@huawei.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Sam Xi <xyzsam@google.com>,
Thomas Richter <tmricht@linux.ibm.com>,
Zhen Lei <thunder.leizhen@huawei.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL] perf tools fixes for v5.10: 4th batch
Date: Sat, 28 Nov 2020 12:30:05 -0300 [thread overview]
Message-ID: <20201128153005.21172-1-acme@kernel.org> (raw)
Hi Linus,
Please consider pulling,
Best regards,
- Arnaldo
The following changes since commit 85a2c56cb4454c73f56d3099d96942e7919b292f:
Merge tag 'pm-5.10-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2020-11-26 11:17:37 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-tools-fixes-for-v5.10-2020-11-28
for you to fetch changes up to a9ffd0484eb4426e6befd07e7be6c01108716302:
perf probe: Change function definition check due to broken DWARF (2020-11-27 14:36:15 -0300)
----------------------------------------------------------------
perf tools for v5.10: 4th batch
- Fix die_entrypc() when DW_AT_ranges DWARF attribute not available.
- Cope with broken DWARF (missing DW_AT_declaration) generated by some recent
gcc versions.
- Do not generate CGROUP metadata events when not asked to in 'perf record'.
- Use proper CPU for shadow stats in 'perf stat'.
- Update copy of libbpf's hashmap.c, silencing tools/perf build warning.
- Fix return value in 'perf diff'.
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/tag/?h=perf-tools-fixes-for-v5.10-2020-11-28
----------------------------------------------------------------
Arnaldo Carvalho de Melo (1):
perf tools: Update copy of libbpf's hashmap.c
Masami Hiramatsu (2):
perf probe: Fix to die_entrypc() returns error correctly
perf probe: Change function definition check due to broken DWARF
Namhyung Kim (2):
perf record: Synthesize cgroup events only if needed
perf stat: Use proper cpu for shadow stats
Zhen Lei (1):
perf diff: Fix error return value in __cmd_diff()
tools/perf/builtin-diff.c | 4 +++-
tools/perf/util/dwarf-aux.c | 28 ++++++++++++++++++++++++++--
tools/perf/util/hashmap.h | 15 +++++++++------
tools/perf/util/probe-finder.c | 3 +--
tools/perf/util/stat-display.c | 5 +----
tools/perf/util/synthetic-events.c | 3 +++
6 files changed, 43 insertions(+), 15 deletions(-)
next reply other threads:[~2020-11-28 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 15:30 Arnaldo Carvalho de Melo [this message]
2020-11-28 22:15 ` [GIT PULL] perf tools fixes for v5.10: 4th batch pr-tracker-bot
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=20201128153005.21172-1-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=hulkci@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=tglx@linutronix.de \
--cc=thunder.leizhen@huawei.com \
--cc=tmricht@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=xyzsam@google.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).