linux-kernel - Re: 2.6.24-rc8-rt1

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: <478F2A46.5070506@grandegger.com>
Date:	Thu, 17 Jan 2008 11:13:26 +0100
From:	Wolfgang Grandegger <wg@...ndegger.com>
To:	Steven Rostedt <rostedt@...dmis.org>
CC:	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.24-rc8-rt1

Steven Rostedt wrote:
> We are pleased to announce the 2.6.24-rc8-rt1 tree, which can be
> downloaded from the location:
> 
>   http://rt.et.redhat.com/download/

It builds and runs fine on my Icecube-MPC5200 board, now also with the
latency tracer enabled. That's great. Still, "cyclictest -n -p80 -i1000"
reports latencies up to 400 us and therefore I tried to trigger and save
a high latency trace using:

  # ./cyclictest -n -p80 -i1000 -b400
  1.21 0.33 0.11 4/42 1048

  T: 0 (  914) P:80 I:1000 C:  38726 Min:     61 Act:  107 Avg:  106
Max:     377
  [   91.042169] (      cyclictest-914  |#0): new 39733427 us user-latency.
  bash-3.00# cat /proc/latency_trace > trace.log

Well, I'm not sure if this is the correct way to do it. Is there some
doc on how to use the latency tracer and interpret the results?
Nevertheless, I have attached the beginning of trace.log. Maybe it rings
an experts bell.

TIA.

Wolfgang.

View attachment "trace-partial.log" of type "text/x-log" (21485 bytes)