[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220512161054.GE14475@alpha.franken.de>
Date: Thu, 12 May 2022 18:10:54 +0200
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Tiezhu Yang <yangtiezhu@...ngson.cn>
Cc: Masami Hiramatsu <mhiramat@...nel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Shuah Khan <shuah@...nel.org>,
Xuefeng Li <lixuefeng@...ngson.cn>, linux-mips@...r.kernel.org,
linux-kselftest@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/2] Modify some code about kprobe
On Fri, May 06, 2022 at 07:02:01PM +0800, Tiezhu Yang wrote:
> v3: no need to change post_kprobe_handler() in patch #2 now,
> sorry for the carelessness.
>
> v2:
> -- only replace __kprobes with NOKPROBE_SYMBOL() in patch #2
> -- update the commit messages
>
> Tiezhu Yang (2):
> selftests/ftrace: Save kprobe_events to test log
> MIPS: Use NOKPROBE_SYMBOL() instead of __kprobes annotation
>
> arch/mips/kernel/kprobes.c | 36 ++++++++++++++--------
> arch/mips/mm/fault.c | 6 ++--
> .../ftrace/test.d/kprobe/multiple_kprobes.tc | 2 ++
> 3 files changed, 30 insertions(+), 14 deletions(-)
>
> --
> 2.1.0
seires applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists