linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: GeunSik Lim <leemgs1@gmail.com>
To: Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Update old Mini-HOWTO for ftrace
Date: Tue, 7 Apr 2009 08:09:50 +0900	[thread overview]
Message-ID: <49b7c2350904061609q7984d5f0u478a092ffcabe12c@mail.gmail.com> (raw)
In-Reply-To: <49b7c2350904060717l1a87cca7p880b6843ea92c702@mail.gmail.com>

Sorry,
I mistake because I don't understand how to submit patch exactly.
I just appended below "singned-off" contents for convenience.
Sorry again.

   Signed-off-by: GeunSik Lim <leemgs1@gmail.com>
   Signed-off-by: Steven Rostedt <srostedt@redhat.com>
   Signed-off-by: Ingo Molnar <mingo@elte.hu>

2009/4/6 GeunSik Lim <leemgs1@gmail.com>:
> I attached patch file again because no-operation is changed
> from "none"word to "nop" word.
>
> for example,
> -       "wakeup preemptirqsoff preemptoff irqsoff ftrace sched_switch none\n\n"
> +       "wakeup preemptirqsoff preemptoff irqsoff function sched_switch nop\n\n"
>
> ./trace_nop.c:struct tracer nop_trace __read_mostly =
>        .name   = "nop",
>        .init           = nop_trace_init,
>        .reset  = nop_trace_reset,
>        .selftest       = trace_selftest_startup_nop,
>        .flags  = &nop_flags,
>        .set_flag       = nop_set_flag
>
>
>
> 2009/4/6 GeunSik Lim <leemgs1@gmail.com>:
>>   Dear Steven,
>>
>>   The author of ftrace(Internal kernel Function Tracer) feature
>> renamed the ftrace tracer
>>    to function to avoid further confusion between the ftrace
>> infrastructure and the
>>    function tracer on Oct-20, 2008.
>>
>>    But, Update of Mini-HOWTO document are still not working
>>    .
>>    Most of the developers often utilize "/debug/tracing/README" file
>> as Mini-HOWTO.
>>    They will confuse definition and usage about ftrace  between
>> README(ftrace) file
>>    and available_tracers(function) file after linux-2.6.27 like me.
>>    And, I want you to append "chrt -f 5 sleep 1" command as simple
>> example for latency.
>>
>>    Signed-off-by: GeunSik Lim <leemgs1@gmail.com>
>>    Signed-off-by: Steven Rostedt <srostedt@redhat.com>
>>    Signed-off-by: Ingo Molnar <mingo@elte.hu>
>> ---
>>  kernel/trace/trace.c |    3 ++-
>>  1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
>> index a0174a4..15f0eec 100644
>> --- a/kernel/trace/trace.c
>> +++ b/kernel/trace/trace.c
>> @@ -2358,7 +2358,7 @@ static const char readme_msg[] =
>>        "# mkdir /debug\n"
>>        "# mount -t debugfs nodev /debug\n\n"
>>        "# cat /debug/tracing/available_tracers\n"
>> -       "wakeup preemptirqsoff preemptoff irqsoff ftrace sched_switch none\n\n"
>> +       "wakeup preemptirqsoff preemptoff irqsoff function
>> sched_switch none\n\n"
>>        "# cat /debug/tracing/current_tracer\n"
>>        "none\n"
>>        "# echo sched_switch > /debug/tracing/current_tracer\n"
>> @@ -2368,6 +2368,7 @@ static const char readme_msg[] =
>>        "noprint-parent nosym-offset nosym-addr noverbose\n"
>>        "# echo print-parent > /debug/tracing/trace_options\n"
>>        "# echo 1 > /debug/tracing/tracing_enabled\n"
>> +       "# chrt -f 5 sleep 1\n"
>>        "# cat /debug/tracing/trace > /tmp/trace.txt\n"
>>        "echo 0 > /debug/tracing/tracing_enabled\n"
>>  ;
>>
>>
>>
>> --
>> Regards,
>> GeunSik Lim
>> --
>> 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/
>>
>
>
>
> --
> Regards,
> GeunSik Lim
> --
> 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/
>



-- 
Regards,
GeunSik Lim
--
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/
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2009-04-06 23:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 14:02 [PATCH] Update old Mini-HOWTO for ftrace GeunSik Lim
2009-04-06 14:17 ` GeunSik Lim
2009-04-06 23:09   ` GeunSik Lim [this message]
2009-04-06 23:32     ` Thomas Gleixner
2009-04-07  0:37       ` Steven Rostedt
2009-04-07  1:25       ` Minchan Kim
2009-04-07  1:26   ` Steven Rostedt
2009-04-07  4:37     ` GeunSik Lim
2009-04-07  1:46 ` Steven Rostedt
2009-04-07  5:08   ` GeunSik Lim

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=49b7c2350904061609q7984d5f0u478a092ffcabe12c@mail.gmail.com \
    --to=leemgs1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=srostedt@redhat.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;
as well as URLs for NNTP newsgroup(s).