linux-kernel - Re: [PATCHv2 1/5] tracing, function_graph: Remove dependency of abstime and duration fields on latency

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1307113373.3667.60.camel@gandalf.stny.rr.com>
Date:	Fri, 03 Jun 2011 11:02:53 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Jiri Olsa <jolsa@...hat.com>
Cc:	fweisbec@...il.com, mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 1/5] tracing, function_graph: Remove dependency of
 abstime and duration fields on latency

On Fri, 2011-06-03 at 16:58 +0200, Jiri Olsa wrote:

> With following commands:
> 	# echo function_graph > ./current_tracer
> 	# cat trace
> 
> This is what it looked like before:
> # tracer: function_graph
> #
> #     TIME        CPU  DURATION                  FUNCTION CALLS
> #      |          |     |   |                     |   |   |   |
>  0)   0.068 us    |          } /* page_add_file_rmap */
>  0)               |          _raw_spin_unlock() {
> ...
> 
> This is what it looks like now:
> # tracer: function_graph
> #
> # CPU  DURATION                  FUNCTION CALLS
> # |     |   |                     |   |   |   |
>  0)   0.068 us    |                } /* add_preempt_count */
>  0)   0.993 us    |              } /* vfsmount_lock_local_lock */
> ...

Much nicer change log.

Thanks!

Seems that every patch I test I stumble across another (unrelated) bug.
And then I get side tracked into fixing that bug. So it may be a while
before I get to these.

-- Steve


--
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/