From: Darren Hart <dvhltc@us.ibm.com>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
Dinakar Guniguntala <dino@in.ibm.com>,
"lkml, " <linux-kernel@vger.kernel.org>
Subject: Re: RFC: methods of sched event tracing and my assumptions
Date: Wed, 02 Sep 2009 14:09:10 -0700 [thread overview]
Message-ID: <4A9EDEF6.2000002@us.ibm.com> (raw)
In-Reply-To: <4A9C5600.8060007@us.ibm.com>
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
prev parent reply other threads:[~2009-09-02 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4A9C1371.6050101@us.ibm.com>
2009-08-31 23:00 ` RFC: methods of sched event tracing and my assumptions Darren Hart
2009-09-02 21:09 ` Darren Hart [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A9EDEF6.2000002@us.ibm.com \
--to=dvhltc@us.ibm.com \
--cc=dino@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).