From: Steven Rostedt <rostedt@goodmis.org>
To: Minfei Huang <mnfhuang@gmail.com>
Cc: mhuang@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: Some confusion about the period of updating new function in
Date: Fri, 11 Dec 2015 09:22:55 -0500 [thread overview]
Message-ID: <20151211092255.3bc7daec@gandalf.local.home> (raw)
In-Reply-To: <20151211105242.GA2826@dhcp-129-201.nay.redhat.com>
On Fri, 11 Dec 2015 18:52:42 +0800
Minfei Huang <mnfhuang@gmail.com> wrote:
> ftrace
> Reply-To:
>
> Hi, Steven.
>
> There is a confusion which blocks my step to go further for ftrace.
>
> Does ftrace guarantee that the replaced function is finished while
> ftrace is replacing the functions? In the other word, is there a
> possible that new function starts to run, while old function is also
> running (maybe this function is called before replacing the function).
No there is no such guarantee. That is up to the function callbacks to
handle themselves.
>
> Function schedule_on_each_cpu maybe fails to excute, if there is no
> enough memory to be allocated? Then kernel may be unstable, if ftrace
> continues, without handling the error, does it?
>
> Previously, I posted a patch to fix this issue, and you nacked it.
>
> [PATCH] workqueue: Add the allocation flags to function
> schedule_on_each_cpu_gfp
Ah that patch. Actually __GFP_NOFAIL is pretty much deprecated. The
real solution is to manually do the schedule on each CPU.
I can whip up a patch for that.
-- Steve
next prev parent reply other threads:[~2015-12-11 14:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 10:52 Some confusion about the period of updating new function in Minfei Huang
2015-12-11 14:22 ` Steven Rostedt [this message]
2015-12-11 14:46 ` Some confusion about the period of updating new function in ftrace Minfei Huang
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=20151211092255.3bc7daec@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhuang@redhat.com \
--cc=mnfhuang@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox