All of lore.kernel.org
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Masami Hiramatsu <mhiramat@kernel.org>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
	Jiri Olsa <jolsa@kernel.org>,
	linux-kernel@vger.kernel.org, aneesh.kumar@linux.ibm.com,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Ian Rogers <irogers@google.com>
Subject: [PATCH 0/2] perf probe: Report permission errors
Date: Sat,  5 Jun 2021 00:30:48 +0900	[thread overview]
Message-ID: <162282064848.448336.15589262399731095367.stgit@devnote2> (raw)

Hi Arnaldo and Ravi,

Here is a couple of patches to improve error message for the permission
errors on perf probe, which we talked in the following thread;

 https://lore.kernel.org/lkml/20210525043744.193297-1-ravi.bangoria@linux.ibm.com/

Thank you,

---

Masami Hiramatsu (2):
      perf/probe: Report possible permission error for map__load failure
      perf/probe: Report permission error for tracefs error


 tools/perf/util/probe-event.c |   25 ++++++++++++++++++++++---
 tools/perf/util/probe-file.c  |    4 ++++
 2 files changed, 26 insertions(+), 3 deletions(-)

--
Masami Hiramatsu (Linaro) <mhiramat@kernel.org>

             reply	other threads:[~2021-06-04 15:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-04 15:30 Masami Hiramatsu [this message]
2021-06-04 15:30 ` [PATCH 1/2] perf/probe: Report possible permission error for map__load failure Masami Hiramatsu
2021-06-04 19:18   ` Arnaldo Carvalho de Melo
2021-06-06  7:11     ` Namhyung Kim
2021-06-07  0:00       ` Masami Hiramatsu
2021-06-08 12:24         ` Arnaldo Carvalho de Melo
2021-06-04 15:31 ` [PATCH 2/2] perf/probe: Report permission error for tracefs error Masami Hiramatsu
2021-06-04 19:18   ` Arnaldo Carvalho de Melo
2021-06-05  3:56     ` Masami Hiramatsu
2021-06-06 15:49       ` [PATCH v2] perf/probe: Report permission error for tracefs access Masami Hiramatsu
2021-06-08 17:13         ` 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=162282064848.448336.15589262399731095367.stgit@devnote2 \
    --to=mhiramat@kernel.org \
    --cc=acme@kernel.org \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.