All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Timer patch V8
Date: Thu, 09 Sep 2004 15:55:03 +0000	[thread overview]
Message-ID: <1094745303.24754.5.camel@tdi> (raw)
In-Reply-To: <Pine.LNX.4.58.0408092115500.22817@schroedinger.engr.sgi.com>

On Thu, 2004-09-09 at 08:28 -0700, Christoph Lameter wrote:
> On Thu, 9 Sep 2004, Alex Williamson wrote:
> 
> > On Wed, 2004-09-08 at 16:23 -0700, Christoph Lameter wrote:
> > > Sorry. I was too superficial when looking at this issue. The following
> > > patch makes the hpet driver build again but I do not have a machine here
> > > that would allow me to test this. Could you verify that this works and get
> > > back to me?
> > >
> >
> >    It builds and boots, so a definite improvement.  I'm not sure how to
> > check if the hpet is being used though.  Thanks,
> 
> Could you run the following program and sent me the output? The precision
> of the REALTIME clock should be the same as the HPET device.
> 

The program reports:

          Gettimeofday() = 1094745228.671790000
           CLOCK_REALTIME=     -17032.000003664 resolution= 3648.000238936
          CLOCK_MONOTONIC=     -17032.000003664 resolution= 3648.000238936
 CLOCK_PROCESS_CPUTIME_ID=          0.000714263 resolution= 0.000000001
  CLOCK_THREAD_CPUTIME_ID=          0.000723913 resolution= 0.000000001


The HPET driver reported a 4ns tick on the timer.  Thanks,

	Alex

-- 
Alex Williamson                             HP Linux & Open Source Lab


  parent reply	other threads:[~2004-09-09 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-10  4:18 Timer patch V8 Christoph Lameter
2004-09-08 19:45 ` Alex Williamson
2004-09-08 20:52 ` Christoph Lameter
2004-09-08 21:23 ` Alex Williamson
2004-09-08 23:23 ` Christoph Lameter
2004-09-09 14:08 ` Robert Picco
2004-09-09 15:01 ` Alex Williamson
2004-09-09 15:28 ` Christoph Lameter
2004-09-09 15:55 ` Alex Williamson [this message]
2004-09-09 16:31 ` Christoph Lameter

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=1094745303.24754.5.camel@tdi \
    --to=alex.williamson@hp.com \
    --cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.