[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54EDADD6.5070404@huawei.com>
Date: Wed, 25 Feb 2015 19:11:18 +0800
From: Wang Nan <wangnan0@...wei.com>
To: Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
CC: <linux@....linux.org.uk>, <tglx@...utronix.de>, <mingo@...hat.com>,
<hpa@...or.com>, <rostedt@...dmis.org>, <ananth@...ibm.com>,
<anil.s.keshavamurthy@...el.com>, <davem@...emloft.net>,
<luto@...capital.net>, <keescook@...omium.org>, <oleg@...hat.com>,
<dave.long@...aro.org>, <tixy@...aro.org>, <nico@...aro.org>,
<yalin.wang2010@...il.com>, <catalin.marinas@....com>,
<Yalin.Wang@...ymobile.com>, <mark.rutland@....com>,
<dave.hansen@...ux.intel.com>, <jkenisto@...ibm.com>,
<anton@...ba.org>, <stefani@...bold.net>, <JBeulich@...e.com>,
<akpm@...ux-foundation.org>, <rusty@...tcorp.com.au>,
<peterz@...radead.org>, <prarit@...hat.com>, <fabf@...net.be>,
<hannes@...xchg.org>, <x86@...nel.org>,
<linux-kernel@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <lizefan@...wei.com>,
"yrl.pp-manager.tt@...achi.com" <yrl.pp-manager.tt@...achi.com>
Subject: Re: [RFC PATCH v3 00/26] Early kprobe: enable kprobes at very early
booting stage.
On 2015/2/20 11:59, Masami Hiramatsu wrote:
> Hi,
>
> Sorry for replying late.
>
> (2015/02/13 14:39), Wang Nan wrote:
>> I fell very sorry for people who reviewed my v2 patch series yesterday
>> at https://lkml.org/lkml/2015/2/12/234 because I didn't provide enough
>> information in commit log. This v3 patch series add those missing
>> commit messages. There are also 2 small fix based on v2:
>>
>> 1. Fixes ftrace_sort_mcount_area. Original patch doesn't work for module.
>> 2. Wraps setting of kprobes_initialized in stop_machine() context.
>
> From the viewpoint of the maintenance, it seems over-engineered and
> not general implementation. Please reconsider just initializing breakpoint
> handler in earlier stage. Since those exceptions may happen anywhere,
> those trap handlers setup very early stage. E.g. on x86, setup_arch()
> setup early_trap_init() at beginning. So we just need to initialize
> kprobes earlier.
I tried as your suggestion. For x86, int3 handler doesn't work correctly until
trap_init(). I don't have enough time to look into this problem today (and I don't
familiar with x86 architecture). Could you please have a look on it?
Thank you.
> I think this is almost enough for debugging, and very general because
> we don't need optprobe for porting to other arch.
>
> And for ftrace-based kprobe, we can just put breakpoint on mcount call at
> beginning. ftrace will need to check and keep it when replacing mcount-call
> with nop. Afterward, we can cleanly update those kprobes with ftrace-based
> kprobe.
>
> So, please start with smaller changes.
>
> Thank you,
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists