From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Kosina <jkosina@suse.cz>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Vojtech Pavlik <vojtech@suse.cz>,
Seth Jennings <sjenning@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: Re: [for-next][PATCH 1/4] ftrace/x86: Add dynamic allocated trampoline for ftrace_ops
Date: Mon, 03 Nov 2014 16:50:21 +0900 [thread overview]
Message-ID: <545733BD.1050708@hitachi.com> (raw)
In-Reply-To: <20141031120158.1f648f7a@gandalf.local.home>
(2014/11/01 1:01), Steven Rostedt wrote:
> On Fri, 31 Oct 2014 14:19:03 +0900
> Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
>
>
>>> + /* Load the contents of ptr into the callback parameter */
>>> + offset = (unsigned long)ptr;
>>> + offset -= (unsigned long)trampoline + op_offset + OP_REF_SIZE;
>>> +
>>> + op_ptr.offset = offset;
>>> +
>>> + /* put in the new offset to the ftrace_ops */
>>> + memcpy(trampoline + op_offset, &op_ptr, OP_REF_SIZE);
>>
>> Would we better call flush_icache_range here?
>
> Do we need to? We just allocated memory to execute. It shouldn't be in
> any CPU cache on the machine.
Indeed, if the trampoline buffer is not re-used (and it seems so),
we don't need to care about it.
OK, I've reviewed that :).
Thank you,
>
> -- Steve
>
>
>>
>> Thank you,
>>
>>> +
>>> + /* ALLOC_TRAMP flags lets us know we created it */
>>> + ops->flags |= FTRACE_OPS_FL_ALLOC_TRAMP;
>>> +
>>> + return (unsigned long)trampoline;
>>> +}
>>
>>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2014-11-03 7:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 18:27 [for-next][PATCH 0/4] ftrace: Add dynamic trampoline support Steven Rostedt
2014-10-27 18:27 ` [for-next][PATCH 1/4] ftrace/x86: Add dynamic allocated trampoline for ftrace_ops Steven Rostedt
2014-10-30 17:00 ` Steven Rostedt
2014-10-31 5:19 ` Masami Hiramatsu
2014-10-31 16:01 ` Steven Rostedt
2014-11-03 7:50 ` Masami Hiramatsu [this message]
2014-11-05 10:28 ` Borislav Petkov
2014-11-06 13:57 ` Steven Rostedt
2014-11-06 15:01 ` Borislav Petkov
2014-10-27 18:27 ` [for-next][PATCH 2/4] ftrace/x86: Show trampoline call function in enabled_functions Steven Rostedt
2014-10-30 17:00 ` Steven Rostedt
2014-11-05 10:42 ` Borislav Petkov
2014-11-06 14:01 ` Steven Rostedt
2014-10-27 18:27 ` [for-next][PATCH 3/4] ftrace/x86: Allow !CONFIG_PREEMPT dynamic ops to use allocated trampolines Steven Rostedt
2014-10-30 17:01 ` Steven Rostedt
2014-11-05 10:46 ` Borislav Petkov
2014-10-27 18:27 ` [for-next][PATCH 4/4] ftrace: Add more information to ftrace_bug() output Steven Rostedt
2014-10-30 17:02 ` Steven Rostedt
2014-11-05 10:49 ` Borislav Petkov
2014-10-29 16:27 ` [for-next][PATCH 0/4] ftrace: Add dynamic trampoline support Jiri Kosina
2014-10-30 16:56 ` Steven Rostedt
2014-10-30 17:08 ` Jiri Kosina
2014-10-31 10:04 ` Masami Hiramatsu
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=545733BD.1050708@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=akpm@linux-foundation.org \
--cc=jkosina@suse.cz \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=sjenning@redhat.com \
--cc=vojtech@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.