From: Ingo Molnar <mingo@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Petr Mladek <pmladek@suse.cz>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
"David S. Miller" <davem@davemloft.net>,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
Ananth NMavinakayanahalli <ananth@in.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Jiri Kosina <jkosina@suse.cz>,
linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails
Date: Mon, 23 Mar 2015 14:53:06 +0100 [thread overview]
Message-ID: <20150323135306.GA25233@gmail.com> (raw)
In-Reply-To: <20150323094317.38dcb601@gandalf.local.home>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Mon, 23 Mar 2015 14:34:42 +0100
> Ingo Molnar <mingo@kernel.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
next prev parent reply other threads:[~2015-03-23 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 14:02 [PATCH v3] kprobes: Disable Kprobe when ftrace arming fails Petr Mladek
2015-03-23 8:54 ` Ingo Molnar
2015-03-23 10:12 ` Petr Mladek
2015-03-23 10:33 ` Ingo Molnar
2015-03-23 12:39 ` Petr Mladek
2015-03-23 13:30 ` Steven Rostedt
2015-03-23 13:34 ` Ingo Molnar
2015-03-23 13:43 ` Steven Rostedt
2015-03-23 13:53 ` Ingo Molnar [this message]
2015-03-23 13:58 ` Steven Rostedt
2015-03-23 16:38 ` Petr Mladek
2015-03-23 16:43 ` Paul E. McKenney
2015-03-23 23:32 ` Jiri Kosina
2015-03-23 22:36 ` Jiri Kosina
2015-03-24 7:59 ` Petr Mladek
2015-03-24 13:36 ` Steven Rostedt
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=20150323135306.GA25233@gmail.com \
--to=mingo@kernel.org \
--cc=ananth@in.ibm.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pmladek@suse.cz \
--cc=rostedt@goodmis.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox