linux-kernel - Re: [PATCH 2/5] trace-cmd: group schedule stacktraces together with --merge

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]

Date:	Wed, 20 May 2015 13:36:14 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Josef Bacik <jbacik@...com>
Cc:	<linux-kernel@...r.kernel.org>, <kernel-team@...com>
Subject: Re: [PATCH 2/5] trace-cmd: group schedule stacktraces together with
 --merge

On Fri, 8 May 2015 15:29:01 -0400
Josef Bacik <jbacik@...com> wrote:

> With --merge we want to be able to merge the scheduling information as well so
> we can see how the whole app spent its time.  This is a little tricky because we
> have to sort based on comm instead of pid.  It works out well enough because we
> store the intermediate information in the per task hash, but we want to group
> the final information together.

If we do the merge at the end, we wont need to worry about this.

-- Steve

> 
> Signed-off-by: Josef Bacik <jbacik@...com>
>
--
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/