From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Shuah Khan <shuah@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Andy Lutomirski <luto@amacapital.net>,
Andrew Morton <akpm@linux-foundation.org>,
Changbin Du <changbin.du@gmail.com>, Jann Horn <jannh@google.com>,
Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@kernel.org>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Nadav Amit <namit@vmware.com>,
Joel Fernandes <joel@joelfernandes.org>,
yhs@fb.com
Subject: Re: [PATCH -tip v8 0/6] tracing/probes: uaccess: Add support user-space access
Date: Tue, 14 May 2019 11:01:13 -0300 [thread overview]
Message-ID: <20190514140113.GI3198@kernel.org> (raw)
In-Reply-To: <20190514140253.1edece79ff72ba47b9a8c72c@kernel.org>
Em Tue, May 14, 2019 at 02:02:53PM +0900, Masami Hiramatsu escreveu:
> On Mon, 13 May 2019 15:38:24 -0300 Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> > Em Fri, May 10, 2019 at 12:12:49AM +0900, Masami Hiramatsu escreveu:
> > > In this version, I fixed some typos/style issues and renamed fields
> > > according to Ingo's comment, and added Ack from Steve.
> > >
> > > Also this version is rebased on the latest -tip/master tree.
> >
> > Ingo, since this touches 'perf probe' and Steven already provided an
> > Acked-by, if you're ok with it I can process these, testing the 'perf
> > probe' changes and then ship it to you in my next pull req, ok?
>
> Thanks Arnaldo! For the perf probe enhancement, it should work on
> the kernel which doesn't support 'u' prefix. :)
Sure, I'll test that case too, i.e. old kernel + new tool, old tool +
new kernel, new tool + new kernel, as usual.
- Arnaldo
prev parent reply other threads:[~2019-05-14 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 15:12 [PATCH -tip v8 0/6] tracing/probes: uaccess: Add support user-space access Masami Hiramatsu
2019-05-09 15:13 ` [PATCH -tip v8 1/6] x86/uaccess: Allow access_ok() in irq context if pagefault_disabled Masami Hiramatsu
2019-05-09 15:13 ` [PATCH -tip v8 2/6] uaccess: Add non-pagefault user-space read functions Masami Hiramatsu
2019-05-09 15:13 ` [PATCH -tip v8 3/6] tracing/probe: Add ustring type for user-space string Masami Hiramatsu
2019-05-14 7:24 ` Ingo Molnar
2019-05-14 10:10 ` Masami Hiramatsu
2019-05-09 15:13 ` [PATCH -tip v8 4/6] tracing/probe: Support user-space dereference Masami Hiramatsu
2019-05-09 15:13 ` [PATCH -tip v8 5/6] selftests/ftrace: Add user-memory access syntax testcase Masami Hiramatsu
2019-05-09 15:14 ` [PATCH -tip v8 6/6] perf-probe: Add user memory access attribute support Masami Hiramatsu
2019-05-13 18:38 ` [PATCH -tip v8 0/6] tracing/probes: uaccess: Add support user-space access Arnaldo Carvalho de Melo
2019-05-14 5:02 ` Masami Hiramatsu
2019-05-14 14:01 ` Arnaldo Carvalho de Melo [this message]
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=20190514140113.GI3198@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=changbin.du@gmail.com \
--cc=jannh@google.com \
--cc=joel@joelfernandes.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namit@vmware.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yhs@fb.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.