[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190509091735.GC90202@gmail.com>
Date: Thu, 9 May 2019 11:17:35 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Shuah Khan <shuah@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org,
Andy Lutomirski <luto@...capital.net>,
Andrew Morton <akpm@...ux-foundation.org>,
Changbin Du <changbin.du@...il.com>,
Jann Horn <jannh@...gle.com>,
Kees Cook <keescook@...omium.org>,
Andy Lutomirski <luto@...nel.org>,
Alexei Starovoitov <alexei.starovoitov@...il.com>,
Nadav Amit <namit@...are.com>,
Joel Fernandes <joel@...lfernandes.org>, yhs@...com
Subject: Re: [PATCH v7 6/6] perf-probe: Add user memory access attribute
support
* Masami Hiramatsu <mhiramat@...nel.org> wrote:
> --- a/tools/perf/util/probe-event.h
> +++ b/tools/perf/util/probe-event.h
> @@ -37,6 +37,7 @@ struct probe_trace_point {
> struct probe_trace_arg_ref {
> struct probe_trace_arg_ref *next; /* Next reference */
> long offset; /* Offset value */
> + bool user; /* User-memory access */
> };
>
> /* kprobe-tracer and uprobe-tracer tracing argument */
> @@ -82,6 +83,7 @@ struct perf_probe_arg {
> char *var; /* Variable name */
> char *type; /* Type name */
> struct perf_probe_arg_field *field; /* Structure fields */
> + bool user; /* User-memory */
Why did the 'access' qualifier get dropped from the second comment?
Also, please name it and related parameters and local variables
'user_access' - in that case no comments are needed and it's all super
clear. Only 'user' is ambiguous really.
Thanks,
ngo
Powered by blists - more mailing lists