All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Torben Hohn <torbenh@gmx.de>,
	linux-kernel@vger.kernel.org, richard.cochran@omicron.at,
	tglx@linutronix.de
Subject: Re: [PATCH 2/3] ptp: add a software clock based on clock_monotonic_raw
Date: Sat, 05 Mar 2011 12:08:07 -0800	[thread overview]
Message-ID: <1299355687.28285.130.camel@work-vm> (raw)
In-Reply-To: <20110304064639.GD3824@riccoc20.at.omicron.at>

On Fri, 2011-03-04 at 07:46 +0100, Richard Cochran wrote:
> On Thu, Mar 03, 2011 at 11:34:04AM -0800, john stultz wrote:
> > On Thu, 2011-03-03 at 18:26 +0100, Torben Hohn wrote:
> > > First version of a software clock. Not very useful yet,
> > > as it doesnt generate events, but at least it allows
> > > for testing the ptp framework without special hardware.
> > 
> > So in the past, I pushed back on Richard for having something similar,
> > as I'm not psyched about duplicating interfaces. However, your
> > implementation is CLOCK_MONOTONIC_RAW instead of CLOCK_REALTIME and it
> > keeps the adjustments internal, I'm not as opposed.
> 
> (Aha! So it is okay after all ;)
> 
> I do think a software only PHC will make it easier for people to get
> started with the new interface. I have been carrying along such a
> patch privately for my own testing.

Consistency is but a hobgoblin... :)

But seriously, do forgive me if I misunderstood your earlier patches
with this respect. I thought it was just exporting CLOCK_REALTIME
directly through a new interface/clockid (which would be duplicative).

thanks
-john



  parent reply	other threads:[~2011-03-05 20:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03 17:26 some patches for the ptp framework Torben Hohn
2011-03-03 17:26 ` [PATCH 1/3] remove __cpuinit from mwait_usable() Torben Hohn
2011-03-03 17:26 ` [PATCH 2/3] ptp: add a software clock based on clock_monotonic_raw Torben Hohn
2011-03-03 19:34   ` john stultz
2011-03-04  6:46     ` Richard Cochran
2011-03-04 11:06       ` torbenh
2011-03-05 20:08       ` john stultz [this message]
2011-03-06 13:28         ` Richard Cochran
2011-03-11 11:13           ` torbenh
2011-03-11 11:37             ` Christian Riesch
2011-03-11 13:38               ` torbenh
2011-03-11 11:56             ` Christian Riesch
2011-03-04  6:42   ` Richard Cochran
2011-03-04 11:30     ` torbenh
2011-03-04 16:10       ` Richard Cochran
2011-03-03 17:26 ` [PATCH 3/3] Check for write permission on FD based posix-clocks Torben Hohn
2011-03-04  7:22   ` Richard Cochran
2011-03-04  9:55     ` Arnd Bergmann
2011-03-04 10:13     ` torbenh
2011-03-11 19:46     ` Thomas Gleixner
2011-03-12 17:23       ` Richard Cochran
2011-03-12 17:35         ` Thomas Gleixner
2011-03-12 20:30   ` [tip:timers/core] posix-clocks: Check write permissions in posix syscalls tip-bot for Torben Hohn
2011-03-04  6:21 ` some patches for the ptp framework Richard Cochran
2011-03-10  7:02   ` Richard Cochran

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=1299355687.28285.130.camel@work-vm \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.cochran@omicron.at \
    --cc=richardcochran@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=torbenh@gmx.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 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.