public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: Milan Svoboda <msvoboda@ra.rockwell.com>,
	linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH] 2.6.17-rt add clockevent to ixp4xx
Date: Thu, 13 Jul 2006 21:07:54 +0200	[thread overview]
Message-ID: <1152817675.24345.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1152801697.22049.7.camel@c-67-180-134-207.hsd1.ca.comcast.net>

On Thu, 2006-07-13 at 07:41 -0700, Daniel Walker wrote:
> On Thu, 2006-07-13 at 10:53 +0000, Milan Svoboda wrote:
> > Hello,
> > 
> > there are patches that enable clock event on ixp4xx platform. This should
> > enable high resolution timers... Option for hrtimers in menuconfig is 
> > also enabled.
> > 
> > I tested it on nanosleep test program (included in attachments) and obtained
> > this results:
> > 
> > requested: 899000 us, got: 899159 us, diff: -159 us
> > requested: 897000 us, got: 897209 us, diff: -209 us
> > requested: 895000 us, got: 899803 us, diff: -4803 us
> > requested: 893000 us, got: 899425 us, diff: -6425 us
> > requested: 891000 us, got: 899806 us, diff: -8806 us
> > requested: 889000 us, got: 890142 us, diff: -1142 us
> > requested: 887000 us, got: 889873 us, diff: -2873 us
> > requested: 885000 us, got: 888096 us, diff: -3096 us
> 
> I'd turn off some of the debugging options, and retest. For instance,
> the pi-list debugging option will cause arbitrary latency, which you
> seem to show in your results. Normally with PREEMPT_RT turned on you
> would expect the timers to trigger within a constant amount of time from
> when they are suppose to.

No, the time differences looks like the high res mode never gets
switched on. its oszillating between 0 and 10ms, which is the usual
behaviour for a non hrt kernel.

Also I would recommend to test without preempt-rt in the first place.
Preempt-rt on ARM is not really well tested, so you dont fight two
battles at once.

	tglx



  reply	other threads:[~2006-07-13 19:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13 10:53 [PATCH] 2.6.17-rt add clockevent to ixp4xx Milan Svoboda
2006-07-13 14:41 ` Daniel Walker
2006-07-13 19:07   ` Thomas Gleixner [this message]
2006-07-13 21:48 ` Kevin Hilman
  -- strict thread matches above, loose matches on Subject: below --
2006-07-14 10:06 Milan Svoboda
2006-07-14 10:27 Milan Svoboda
2006-07-14 10:36 Milan Svoboda
2006-07-14 21:02 ` Kevin Hilman

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=1152817675.24345.2.camel@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=dwalker@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=msvoboda@ra.rockwell.com \
    /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