mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org, John Stultz <johnstul@us.ibm.com>,
	Lee Revell <rlrevell@joe-job.com>,
	Martin Ridgeway <mridge@users.sourceforge.net>
Subject: Re: 2.6.16-rc6-rt7
Date: Sat, 18 Mar 2006 13:58:01 +0100	[thread overview]
Message-ID: <1142686681.17279.78.camel@localhost.localdomain> (raw)
In-Reply-To: <20060318125425.GA32662@smtp.west.cox.net>

On Sat, 2006-03-18 at 05:54 -0700, Tom Rini wrote:
> On Sat, Mar 18, 2006 at 11:37:19AM +0100, Thomas Gleixner wrote:
> > On Fri, 2006-03-17 at 16:36 -0700, Tom Rini wrote:
> > > On Thu, Mar 16, 2006 at 10:56:08AM +0100, Ingo Molnar wrote:
> > > 
> > > > i have released the 2.6.16-rc6-rt7 tree, which can be downloaded from 
> > > > the usual place:
> > > > 
> > > >    http://redhat.com/~mingo/realtime-preempt/
> > > 
> > > I was wondering, is it normal for the nanosleep02 and alarm02 LTP tests
> > > to fail?  For sometime I've seen these tests fail from time to time with
> > > the -RT patch but not the regular kernel.
> > 
> > The nanosleep02 failure is incorrect due to rounding errors in the test
> > code.
> [snip]
> > This never happens on vanilla, as the nanosleep is rounded to the next
> > jiffie. -rt has high resolution timers which are delivered accurate, so
> > the rounding errors of the testcode surface.
> 
> Thanks!  Any ideas about the alarm02 test?

Yes. Its due (unsigned int) -> long conversion and a missing check.

That one affects mainline as well. I'm fixing this one right now. Patch
follows.

	tglx






      reply	other threads:[~2006-03-18 12:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-16  9:56 2.6.16-rc6-rt7 Ingo Molnar
2006-03-16 17:39 ` 2.6.16-rc6-rt7 David Brown
2006-03-16 17:50   ` 2.6.16-rc6-rt7 Thomas Gleixner
2006-03-17  8:20     ` 2.6.16-rc6-rt7 Ingo Molnar
2006-03-16 21:42 ` 2.6.16-rc6-rt7 Michal Piotrowski
2006-03-17 23:36 ` 2.6.16-rc6-rt7 Tom Rini
2006-03-18  8:57   ` 2.6.16-rc6-rt7 Ingo Molnar
2006-03-18 12:54     ` 2.6.16-rc6-rt7 Tom Rini
2006-03-18 10:37   ` 2.6.16-rc6-rt7 Thomas Gleixner
2006-03-18 12:54     ` 2.6.16-rc6-rt7 Tom Rini
2006-03-18 12:58       ` Thomas Gleixner [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=1142686681.17279.78.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mridge@users.sourceforge.net \
    --cc=rlrevell@joe-job.com \
    --cc=trini@kernel.crashing.org \
    /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

all inboxes | Powered by JetHome®