From: Thomas Richter <tmricht@linux.ibm.com>
To: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
acme@kernel.org
Cc: brueckner@linux.vnet.ibm.com, heiko.carstens@de.ibm.com,
Thomas Richter <tmricht@linux.ibm.com>
Subject: [PATCH 0/3] Fix OOM in perf report on s390
Date: Wed, 22 May 2019 16:45:58 +0200 [thread overview]
Message-ID: <20190522144601.50763-1-tmricht@linux.ibm.com> (raw)
This patch set fixes OOM scenarios on s390 when commands
perf top or perf report are executed. This often happens
when debuginfo packages are not installed. Root users
and non-root users are both affected.
Patch 1: Do not allocate memory for histograms when
the symbol is not of type function.
Patch 2: Reduce the gap between kernel end and and first
module start address on perf record.
Patch 3: Create module maps for non-root user during
perf record on s390.
Thomas Richter (3):
perf report: Fix OOM error in TUI mode on s390
perf record: Fix kallsym map size for s390
perf record: Fix s390 missing module symbol and warning for non-root
users
tools/perf/arch/s390/util/machine.c | 9 ++++++---
tools/perf/util/annotate.c | 2 +-
tools/perf/util/event.c | 4 ++--
tools/perf/util/machine.c | 29 +++++++++++++++++++++++------
4 files changed, 32 insertions(+), 12 deletions(-)
--
2.19.1
next reply other threads:[~2019-05-22 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-22 14:45 Thomas Richter [this message]
2019-05-22 14:45 ` [PATCH 1/3] perf report: Fix OOM error in TUI mode on s390 Thomas Richter
2019-05-22 18:08 ` Arnaldo Carvalho de Melo
2019-05-23 8:12 ` Thomas-Mich Richter
2019-05-22 14:46 ` [PATCH 2/3] perf record: Fix kallsym map size for s390 Thomas Richter
2019-05-22 14:46 ` [PATCH 3/3] perf record: Fix s390 missing module symbol and warning for non-root users Thomas Richter
2019-05-22 18:03 ` Arnaldo Carvalho de Melo
2019-05-28 21:30 ` [tip:perf/urgent] " tip-bot for Thomas Richter
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=20190522144601.50763-1-tmricht@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=acme@kernel.org \
--cc=brueckner@linux.vnet.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.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 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).