public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Magnus Lynch <maglyx@gmail.com>
Cc: Clemens Ladisch <clemens@ladisch.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hpet: factor timer allocate from open
Date: Wed, 03 Mar 2010 08:26:09 -0800	[thread overview]
Message-ID: <1267633569.1947.23.camel@work-vm> (raw)
In-Reply-To: <be233a491003030107u3d9fae9cvc6b4a25db7060ec9@mail.gmail.com>

On Wed, 2010-03-03 at 01:07 -0800, Magnus Lynch wrote:
> On Mon, Mar 1, 2010 at 12:59 PM, john stultz <johnstul@us.ibm.com> wrote:
> > Yes, CLOCK_MONOTONIC_RAW was added specifically to create a hardware
> > agnostic interface that provided a 1:1 ratio to the hardware cycle
> > counter used by the timekeeping core. No NTP corrections or slewing
> > are applied and it isn't affected by settimeofday calls.
> >
> > Let me know if you run into any trouble with it.
> > thanks
> 
> Actually I did run into trouble. CLOCK_MONOTONIC_RAW is defined in
> linux/time.h and including that creates a lot of redefinition
> conflicts with time.h. I see the linux/ includes aren't intended for
> user space code.

Oh, right. Sorry about that, Glibc still hasn't picked these up.

I'll have to chase down how to get that done. 

For now, you can just add the following to your code:
#define CLOCK_MONOTONIC_RAW		4

Thanks for bringing it up!
-john



  reply	other threads:[~2010-03-03 16:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01  5:30 [PATCH] hpet: factor timer allocate from open Magnus Lynch
2010-03-01  9:59 ` Clemens Ladisch
2010-03-01 20:24   ` Magnus Lynch
2010-03-01 20:59     ` john stultz
2010-03-03  9:07       ` Magnus Lynch
2010-03-03 16:26         ` john stultz [this message]
2010-03-10  2:47           ` Magnus Lynch
2010-03-04  2:59   ` Magnus Lynch
2010-03-04  8:43     ` Clemens Ladisch
2010-03-08  0:04       ` Magnus Lynch
2010-03-16 16:01         ` Clemens Ladisch
2010-03-18 19:11         ` Andrew Morton
2010-03-19  4:06           ` Magnus Lynch
2010-03-22 22:21             ` Andrew Morton
2010-03-23  2:02               ` Magnus Lynch

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=1267633569.1947.23.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maglyx@gmail.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