[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20191114132213.5419-1-ravi.bangoria@linux.ibm.com>
Date: Thu, 14 Nov 2019 18:52:10 +0530
From: Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
To: acme@...nel.org
Cc: jolsa@...hat.com, kan.liang@...el.com, mark.rutland@....com,
alexander.shishkin@...ux.intel.com, namhyung@...nel.org,
ak@...ux.intel.com, yao.jin@...ux.intel.com,
linux-kernel@...r.kernel.org,
Ravi Bangoria <ravi.bangoria@...ux.ibm.com>
Subject: [PATCH v2 0/3] perf report: Few fixes
v1: https://lore.kernel.org/r/20191112054946.5869-1-ravi.bangoria@linux.ibm.com
v1 fixed a segfault when -F phys_daddr is used in perf report without
--mem-mode. Arnaldo suggested to bail out the option completely in
such case instead of showing 0 values.
Ravi Bangoria (3):
perf hists: Replace pr_err with ui__error
perf report: Make -F more strict like -s
perf report: Error out for mem mode fields if mem info is not
available
tools/perf/builtin-report.c | 8 ++++++++
tools/perf/util/sort.c | 16 +++++++++++-----
2 files changed, 19 insertions(+), 5 deletions(-)
--
2.21.0
Powered by blists - more mailing lists