[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LNX.2.00.1101080004420.26685@pobox.suse.cz>
Date: Sat, 8 Jan 2011 00:04:52 +0100 (CET)
From: Jiri Kosina <jkosina@...e.cz>
To: Tao Ma <tm@....ma>
Cc: linux-kernel@...r.kernel.org, Li Zefan <lizf@...fujitsu.com>,
Randy Dunlap <rdunlap@...otime.net>
Subject: Re: [PATCH] Documentation/trace/events.txt: Remove obsolete
sched_signal_send.
On Wed, 5 Jan 2011, Tao Ma wrote:
> From: Tao Ma <boyu.mt@...bao.com>
>
> 'sched_signal_send' doesn't exist in the kernel now. Replace it
> with 'signal_generate' so that the example in events.txt can be
> executed successfully.
>
> I also change some /debug to /sys/kernel/debug which is debugfs'
> default mount directory now(similar to commit 52ad51e).
>
> Cc: Li Zefan <lizf@...fujitsu.com>
> Cc: Randy Dunlap <rdunlap@...otime.net>
> Cc: Jiri Kosina <jkosina@...e.cz>
> Signed-off-by: Tao Ma <boyu.mt@...bao.com>
> ---
> Documentation/trace/events.txt | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/trace/events.txt b/Documentation/trace/events.txt
> index 09bd8e9..b510564 100644
> --- a/Documentation/trace/events.txt
> +++ b/Documentation/trace/events.txt
> @@ -125,7 +125,7 @@ is the size of the data item, in bytes.
> For example, here's the information displayed for the 'sched_wakeup'
> event:
>
> -# cat /debug/tracing/events/sched/sched_wakeup/format
> +# cat /sys/kernel/debug/tracing/events/sched/sched_wakeup/format
>
> name: sched_wakeup
> ID: 60
> @@ -201,19 +201,19 @@ to the 'filter' file for the given event.
>
> For example:
>
> -# cd /debug/tracing/events/sched/sched_wakeup
> +# cd /sys/kernel/debug/tracing/events/sched/sched_wakeup
> # echo "common_preempt_count > 4" > filter
>
> A slightly more involved example:
>
> -# cd /debug/tracing/events/sched/sched_signal_send
> +# cd /sys/kernel/debug/tracing/events/signal/signal_generate
> # echo "((sig >= 10 && sig < 15) || sig == 17) && comm != bash" > filter
>
> If there is an error in the expression, you'll get an 'Invalid
> argument' error when setting it, and the erroneous string along with
> an error message can be seen by looking at the filter e.g.:
>
> -# cd /debug/tracing/events/sched/sched_signal_send
> +# cd /sys/kernel/debug/tracing/events/signal/signal_generate
> # echo "((sig >= 10 && sig < 15) || dsig == 17) && comm != bash" > filter
> -bash: echo: write error: Invalid argument
> # cat filter
Applied, thanks for catching this.
--
Jiri Kosina
SUSE Labs, Novell Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists