<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in ftrace.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6644c654 - ftrace: Cleanup ftrace_dyn_arch_init()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#6644c654</link>
        <description>ftrace: Cleanup ftrace_dyn_arch_init()Most of ARCHs use empty ftrace_dyn_arch_init(), introduce a weak commonftrace_dyn_arch_init() to cleanup them.Link: https://lkml.kernel.org/r/20210909090216.1955240-1-o451686892@gmail.comAcked-by: Heiko Carstens &lt;hca@linux.ibm.com&gt; (s390)Acked-by: Helge Deller &lt;deller@gmx.de&gt; (parisc)Signed-off-by: Weizhao Ouyang &lt;o451686892@gmail.com&gt;Signed-off-by: Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Thu, 09 Sep 2021 09:02:16 +0000</pubDate>
        <dc:creator>Weizhao Ouyang &lt;o451686892@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>556763e5 - microblaze: function_graph: Simplify with function_graph_enter()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#556763e5</link>
        <description>microblaze: function_graph: Simplify with function_graph_enter()The function_graph_enter() function does the work of calling the functiongraph hook function and the management of the shadow stack, simplifying thework done in the architecture dependent prepare_ftrace_return().Have microblaze use the new code, and remove the shadow stack management as well ashaving to set up the trace structure.This is needed to prepare for a fix of a design bug on how the curr_ret_stackis used.Cc: Michal Simek &lt;monstr@monstr.eu&gt;Cc: stable@kernel.orgFixes: 03274a3ffb449 (&quot;tracing/fgraph: Adjust fgraph depth before calling trace return callback&quot;)Reviewed-by: Masami Hiramatsu &lt;mhiramat@kernel.org&gt;Signed-off-by: Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Sun, 18 Nov 2018 22:23:30 +0000</pubDate>
        <dc:creator>Steven Rostedt (VMware) &lt;rostedt@goodmis.org&gt;</dc:creator>
    </item>
<item>
        <title>9a7c348b - ftrace: Add return address pointer to ftrace_ret_stack</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#9a7c348b</link>
        <description>ftrace: Add return address pointer to ftrace_ret_stackStoring this value will help prevent unwinders from getting out of syncwith the function graph tracer ret_stack.  Now instead of needing astateful iterator, they can compare the return address pointer to findthe right ret_stack entry.Note that an array of 50 ftrace_ret_stack structs is allocated for everytask.  So when an arch implements this, it will add either 200 or 400bytes of memory usage per task (depending on whether it&apos;s a 32-bit or64-bit platform).Signed-off-by: Josh Poimboeuf &lt;jpoimboe@redhat.com&gt;Acked-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;Cc: Andy Lutomirski &lt;luto@amacapital.net&gt;Cc: Andy Lutomirski &lt;luto@kernel.org&gt;Cc: Borislav Petkov &lt;bp@alien8.de&gt;Cc: Brian Gerst &lt;brgerst@gmail.com&gt;Cc: Byungchul Park &lt;byungchul.park@lge.com&gt;Cc: Denys Vlasenko &lt;dvlasenk@redhat.com&gt;Cc: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;Cc: H. Peter Anvin &lt;hpa@zytor.com&gt;Cc: Kees Cook &lt;keescook@chromium.org&gt;Cc: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;Cc: Nilay Vaish &lt;nilayvaish@gmail.com&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Thomas Gleixner &lt;tglx@linutronix.de&gt;Link: http://lkml.kernel.org/r/a95cfcc39e8f26b89a430c56926af0bb217bc0a1.1471607358.git.jpoimboe@redhat.comSigned-off-by: Ingo Molnar &lt;mingo@kernel.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Fri, 19 Aug 2016 11:52:57 +0000</pubDate>
        <dc:creator>Josh Poimboeuf &lt;jpoimboe@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>e1dc5007 - microblaze: ftrace: Add call to ftrace_graph_is_dead() in function graph code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#e1dc5007</link>
        <description>microblaze: ftrace: Add call to ftrace_graph_is_dead() in function graph codeftrace_stop() is going away as it disables parts of function tracingthat affects users that should not be affected. But ftrace_graph_stop()is built on ftrace_stop(). Here&apos;s another example of killing all offunction tracing because something went wrong with function graphtracing.Instead of disabling all users of function tracing on function grapherror, disable only function graph tracing. To do this, the arch codemust call ftrace_graph_is_dead() before it implements function graph.Link: http://lkml.kernel.org/r/53C8D874.9090601@monstr.euTested-by: Michal Simek &lt;monstr@monstr.eu&gt;Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Wed, 25 Jun 2014 13:43:31 +0000</pubDate>
        <dc:creator>Steven Rostedt (Red Hat) &lt;rostedt@goodmis.org&gt;</dc:creator>
    </item>
<item>
        <title>3a36cb11 - ftrace: Do not pass data to ftrace_dyn_arch_init</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#3a36cb11</link>
        <description>ftrace: Do not pass data to ftrace_dyn_arch_initAs the data parameter is not really used by any ftrace_dyn_arch_init,remove that from ftrace_dyn_arch_init. This also removes the addrlocal variable from ftrace_init which is now unused.Note the documentation was imprecise as it did not suggest to set(*data) to 0.Link: http://lkml.kernel.org/r/1393268401-24379-4-git-send-email-jslaby@suse.czCc: Frederic Weisbecker &lt;fweisbec@gmail.com&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: linux-arch@vger.kernel.orgSigned-off-by: Jiri Slaby &lt;jslaby@suse.cz&gt;Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Mon, 24 Feb 2014 18:59:59 +0000</pubDate>
        <dc:creator>Jiri Slaby &lt;jslaby@suse.cz&gt;</dc:creator>
    </item>
<item>
        <title>af64a7cb - ftrace: Pass retval through return in ftrace_dyn_arch_init()</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#af64a7cb</link>
        <description>ftrace: Pass retval through return in ftrace_dyn_arch_init()No architecture uses the &quot;data&quot; parameter in ftrace_dyn_arch_init() in anyway, it just sets the value to 0. And this is used as a return valuein the caller -- ftrace_init, which just checks the retval againstzero.Note there is also &quot;return 0&quot; in every ftrace_dyn_arch_init.  So it isenough to check the retval and remove all the indirect sets of data onall archs.Link: http://lkml.kernel.org/r/1393268401-24379-3-git-send-email-jslaby@suse.czCc: linux-arch@vger.kernel.orgSigned-off-by: Jiri Slaby &lt;jslaby@suse.cz&gt;Signed-off-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Mon, 24 Feb 2014 18:59:58 +0000</pubDate>
        <dc:creator>Jiri Slaby &lt;jslaby@suse.cz&gt;</dc:creator>
    </item>
<item>
        <title>6bd55f0b - microblaze: Fix coding style issues</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#6bd55f0b</link>
        <description>microblaze: Fix coding style issuesFix coding style issues reported by checkpatch.pl.Signed-off-by: Michal Simek &lt;monstr@monstr.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Thu, 27 Dec 2012 09:40:38 +0000</pubDate>
        <dc:creator>Michal Simek &lt;monstr@monstr.eu&gt;</dc:creator>
    </item>
<item>
        <title>9e1491de - microblaze: Fix ftrace</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#9e1491de</link>
        <description>microblaze: Fix ftrace- Do not trace idle loop which takes a lot time- Fix cache handling in generic ftrace code- Do not trace lib functions ashldi3, ashrdi3, lshrdi3  Functions are called from generic ftrace code which  can&apos;t be tracedSigned-off-by: Michal Simek &lt;monstr@monstr.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Fri, 18 Mar 2011 12:52:27 +0000</pubDate>
        <dc:creator>Michal Simek &lt;monstr@monstr.eu&gt;</dc:creator>
    </item>
<item>
        <title>d2bf98e6 - microblaze: Fix ftrace_update_ftrace_func panic</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#d2bf98e6</link>
        <description>microblaze: Fix ftrace_update_ftrace_func panicThe Microblaze dynamic ftrace code assumes a call ordering that is not metin all scenarios. Specifically, executing a command similar to:  echo 105 &gt; /sys/kernel/debug/tracing/set_ftrace_pidbefore any other tracing-related commands results in a kernel panic:  BUG: failure at arch/microblaze/kernel/ftrace.c:198/ftrace_update_ftrace_func()!Recoding ftrace_update_ftrace_func() to use &amp;ftrace_caller directly eliminatesthe need to capture its address elsewhere (and thus rely on a particular callsequence).Signed-off-by: Steven J. Magnani &lt;steve@digidescorp.com&gt;Signed-off-by: Michal Simek &lt;monstr@monstr.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Fri, 02 Apr 2010 18:29:39 +0000</pubDate>
        <dc:creator>Steven J. Magnani &lt;steve@digidescorp.com&gt;</dc:creator>
    </item>
<item>
        <title>4f911b0d - microblaze: ftrace: Add dynamic function graph tracer</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#4f911b0d</link>
        <description>microblaze: ftrace: Add dynamic function graph tracerThis patch add support for dynamic function graph tracer.There is one my expactation that I can do flush_icache afterall code modification. On microblaze is this safer than doflush for every entry. For icache is used name flush butcorrect should be invalidation - this will be fix in upcommingnew cache implementaion and WB support.Signed-off-by: Michal Simek &lt;monstr@monstr.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Mon, 16 Nov 2009 09:34:15 +0000</pubDate>
        <dc:creator>Michal Simek &lt;monstr@monstr.eu&gt;</dc:creator>
    </item>
<item>
        <title>a0d3e665 - microblaze: ftrace: add function graph support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#a0d3e665</link>
        <description>microblaze: ftrace: add function graph supportFor more information look at Documentation/trace folder.Signed-off-by: Michal Simek &lt;monstr@monstr.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Mon, 16 Nov 2009 09:32:10 +0000</pubDate>
        <dc:creator>Michal Simek &lt;monstr@monstr.eu&gt;</dc:creator>
    </item>
<item>
        <title>7d241ff0 - microblaze: ftrace: Add dynamic trace support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/arch/microblaze/kernel/ftrace.c#7d241ff0</link>
        <description>microblaze: ftrace: Add dynamic trace supportWith dynamic function tracer, by default, _mcount is defined as an&quot;empty&quot; function, it returns directly without any more action. Whenenabling it in user-space, it will jump to a real tracingfunction(ftrace_caller), and do the real job for us.Differ from the static function tracer, dynamic function tracer providestwo functions ftrace_make_call()/ftrace_make_nop() to enable/disable thetracing of some indicated kernel functions(set_ftrace_filter).In the kernel version, there is only one &quot;_mcount&quot; string for everykernel function, so, we just need to match this one in mcount_regex ofscripts/recordmcount.pl.For more information please look at code and Documentation/trace folder.Steven ACK that scripts/recordmcount.pl part.Acked-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;Signed-off-by: Michal Simek &lt;monstr@monstr.eu&gt;

            List of files:
            /linux-6.15/arch/microblaze/kernel/ftrace.c</description>
        <pubDate>Thu, 10 Dec 2009 13:15:44 +0000</pubDate>
        <dc:creator>Michal Simek &lt;monstr@monstr.eu&gt;</dc:creator>
    </item>
</channel>
</rss>
