linux-kernel - Re: RFC: methods of sched event tracing and my assumptions

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] [day] [month] [year] [list]

Message-ID: <4A9EDEF6.2000002@us.ibm.com>
Date:	Wed, 02 Sep 2009 14:09:10 -0700
From:	Darren Hart <dvhltc@...ibm.com>
To:	linux-rt-users <linux-rt-users@...r.kernel.org>
CC:	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Dinakar Guniguntala <dino@...ibm.com>,
	"lkml, " <linux-kernel@...r.kernel.org>
Subject: Re: RFC: methods of sched event tracing and my assumptions

Darren Hart wrote:
> 
> After some gentle resistance to CVS and non-single-file testcases, I 
> prepared a standalone prio-wake-min.c.  It ran to completion on linus 
> with slightly fewer wakeups than the LTP version (I removed a number of 
> things that weren't strictly necessary for this specific exercise), png 
> attached.  It's hung part way through the scripts on rt though.  I'll be 
> looking into that, but in case you prefer to look at this version, it is 
> available here:
> 
> http://dvhart.com/darren/linux/prio-wake-min.c

I have just now updated this test to fix a possible race when using a 
requeue PI enabled glibc (likely a bug in glibc) which also reduces the 
tests runtime from 1s to about 15ms (yeah, the sleep loops were rather 
stupid in the original version :/).

Thanks,

-- 
Darren Hart
IBM Linux Technology Center
Real-Time Linux Team
--
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/