[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150323135306.GA25233@gmail.com>
Date: Mon, 23 Mar 2015 14:53:06 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Petr Mladek <pmladek@...e.cz>,
Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
"David S. Miller" <davem@...emloft.net>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
Ananth NMavinakayanahalli <ananth@...ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...hat.com>, Jiri Kosina <jkosina@...e.cz>,
linux-kernel@...r.kernel.org,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Subject: Re: [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails
* Steven Rostedt <rostedt@...dmis.org> wrote:
> On Mon, 23 Mar 2015 14:34:42 +0100
> Ingo Molnar <mingo@...nel.org> wrote:
> >
> > Even if it was documented (it isn't), it's pretty weird terminology -
> > please use clearer formulations, like 'patched function' or 'unpatched
> > function' or 'function with pending patch'. No need to redefine
> > existing words in a weird fashion just to create the appearance of
> > being special ...
> >
>
> I think it has to do with their RCU like patching functionality,
> where some tasks are still executing the old function and others are
> executing the new function. [...]
That would be the 'function with pending patch' state in my
description above.
Thanks,
Ingo
--
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