public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Hounschell <markh@compro.net>
To: tglx@linutronix.de
Cc: linux-kerneL@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: RT exec for exercising RT kernel capabilities
Date: Thu, 08 Jun 2006 16:50:23 -0400	[thread overview]
Message-ID: <44888D8F.2000404@compro.net> (raw)
In-Reply-To: <1149795975.5257.83.camel@localhost.localdomain>

Thomas Gleixner wrote:
> Mark,
> 
> On Thu, 2006-06-08 at 15:12 -0400, Mark Hounschell wrote:
>> With the ongoing work being done to rt kernel enhancements by Ingo and friends,
>> I would like to offer the use of a user land test (rt-exec). The rt-exec tests
>> well the deterministic real-time capabilities of a computer. Maybe it could
>> useful in some way to the effort or to anyone interested in making this type of
>> determination about their kernel/computer.
>>
>> A README describing the rt-exec can be found at
>> ftp://ftp.compro.net/public/rt-exec/README
>>
>> It can be downloaded from
>> ftp://ftp.compro.net/public/rt-exec/rt-exec-1.0.0.tar.bz2
>>
>> Complaints, comments, or suggestions welcome.
> 
> Nice tool. 
> 
> Some remarks. You can build high resolution timer support without the
> extra lib package from the HRT sourceforge site. You need a recent glibc
> and  some quirks in the source. See the cyclictest program I'm using.
> http://www.tglx.de/projects/misc/cyclictest/cyclictest-v0.8.tar.bz2
> 

I didn't realize that. Right you are.

> It would also be cute to add tests for the PI support for
> pthread_mutexes.
> 
> 	tglx

I'm not sure what one needs to do in user land to actually test that but I'll
investigate.

Thanks
Mark


  reply	other threads:[~2006-06-08 20:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-08 19:12 RT exec for exercising RT kernel capabilities Mark Hounschell
2006-06-08 19:46 ` Thomas Gleixner
2006-06-08 20:50   ` Mark Hounschell [this message]
2006-06-09 11:53     ` Mark Hounschell
2006-06-09 20:04       ` Mark Hounschell
2006-06-09 20:11         ` Thomas Gleixner
2006-06-09  9:15 ` Serge Noiraud
2006-06-09 17:20   ` Lee Revell
2006-06-10  9:50 ` Antonio
2006-06-13 14:13 ` Serge Noiraud
2006-06-13 14:34   ` Mark Hounschell
2006-06-13 14:48     ` Serge Noiraud
2006-06-13 14:53       ` Mark Hounschell
2006-06-13 16:24         ` Mark Hounschell
2006-07-14 22:34 ` Lee Revell
2006-07-15  2:04   ` Thomas Gleixner
2006-07-15  2:10     ` Lee Revell
2006-07-17 14:20       ` Mark Hounschell
2006-07-21 18:17         ` Lee Revell
2006-10-02 22:27       ` Lee Revell
2006-10-02 22:39         ` Thomas Gleixner
2006-10-03 11:14           ` Mark Hounschell

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=44888D8F.2000404@compro.net \
    --to=markh@compro.net \
    --cc=linux-kerneL@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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