All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Cochran <richardcochran@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v4 1/4] Produce system time from correlated clocksource
Date: Tue, 13 Oct 2015 07:26:13 +0200	[thread overview]
Message-ID: <20151013052613.GB2437@netboy> (raw)
In-Reply-To: <1444675522-4198-2-git-send-email-christopher.s.hall@intel.com>

On Mon, Oct 12, 2015 at 11:45:19AM -0700, Christopher S. Hall wrote:
> +int get_correlated_timestamp(struct correlated_ts *crt,
> +			     struct correlated_cs *crs)
> +{
> +	struct timekeeper *tk = &tk_core.timekeeper;
> +	unsigned long seq;
> +	cycles_t cycles, cycles_now, cycles_last;
> +	ktime_t base;
> +	s64 nsecs;
> +	int ret;
> +
> +	do {
> +		seq = read_seqcount_begin(&tk_core.seq);
> +		/*
> +		 * Verify that the correlated clocksoure is related to
> +		 * the currently installed timekeeper clocksoure
> +		 */
> +		if (tk->tkr_mono.clock != crs->related_cs)
> +			return -ENODEV;
> +
> +		/*
> +		 * Get a timestamp from the device if get_ts is non-NULL
> +		 */
> +		if( crt->get_ts ) {

CodingStyle.

> +			ret = crt->get_ts(crt);
> +			if (ret)
> +				return ret;
> +		}
> +
> +		/*
> +		 * Convert the timestamp to timekeeper clock cycles
> +		 */
> +		cycles = crs->convert(crs, crt->system_ts);
> +
> +		/*
> +		 * If we have get_ts is valid, we know the cycles value
> +		 * value is up to date and we can just do the conversion
> +		 */
> +		if( crt->get_ts )

Ditto.

> +			goto do_convert;
> +

Thanks,
Richard

WARNING: multiple messages have this Message-ID (diff)
From: Richard Cochran <richardcochran@gmail.com>
To: "Christopher S. Hall" <christopher.s.hall@intel.com>
Cc: jeffrey.t.kirsher@intel.com, hpa@zytor.com, mingo@redhat.com,
	tglx@linutronix.de, john.stultz@linaro.org, peterz@infradead.org,
	x86@kernel.org, intel-wired-lan@lists.osuosl.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	kevin.b.stanton@intel.com
Subject: Re: [PATCH v4 1/4] Produce system time from correlated clocksource
Date: Tue, 13 Oct 2015 07:26:13 +0200	[thread overview]
Message-ID: <20151013052613.GB2437@netboy> (raw)
In-Reply-To: <1444675522-4198-2-git-send-email-christopher.s.hall@intel.com>

On Mon, Oct 12, 2015 at 11:45:19AM -0700, Christopher S. Hall wrote:
> +int get_correlated_timestamp(struct correlated_ts *crt,
> +			     struct correlated_cs *crs)
> +{
> +	struct timekeeper *tk = &tk_core.timekeeper;
> +	unsigned long seq;
> +	cycles_t cycles, cycles_now, cycles_last;
> +	ktime_t base;
> +	s64 nsecs;
> +	int ret;
> +
> +	do {
> +		seq = read_seqcount_begin(&tk_core.seq);
> +		/*
> +		 * Verify that the correlated clocksoure is related to
> +		 * the currently installed timekeeper clocksoure
> +		 */
> +		if (tk->tkr_mono.clock != crs->related_cs)
> +			return -ENODEV;
> +
> +		/*
> +		 * Get a timestamp from the device if get_ts is non-NULL
> +		 */
> +		if( crt->get_ts ) {

CodingStyle.

> +			ret = crt->get_ts(crt);
> +			if (ret)
> +				return ret;
> +		}
> +
> +		/*
> +		 * Convert the timestamp to timekeeper clock cycles
> +		 */
> +		cycles = crs->convert(crs, crt->system_ts);
> +
> +		/*
> +		 * If we have get_ts is valid, we know the cycles value
> +		 * value is up to date and we can just do the conversion
> +		 */
> +		if( crt->get_ts )

Ditto.

> +			goto do_convert;
> +

Thanks,
Richard

  parent reply	other threads:[~2015-10-13  5:26 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 18:45 [Intel-wired-lan] [PATCH v4 0/4] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2015-10-12 18:45 ` Christopher S. Hall
2015-10-12 18:45 ` [Intel-wired-lan] [PATCH v4 1/4] Produce system time from correlated clocksource Christopher S. Hall
2015-10-12 18:45   ` Christopher S. Hall
2015-10-13  4:58   ` [Intel-wired-lan] " Richard Cochran
2015-10-13  4:58     ` Richard Cochran
2015-10-13  7:51     ` [Intel-wired-lan] " Thomas Gleixner
2015-10-13  7:51       ` Thomas Gleixner
2015-10-13  8:31       ` [Intel-wired-lan] " Richard Cochran
2015-10-13  8:31         ` Richard Cochran
2015-10-13 19:15         ` [Intel-wired-lan] " Thomas Gleixner
2015-10-13 19:15           ` Thomas Gleixner
2015-10-13 21:12           ` [Intel-wired-lan] " Richard Cochran
2015-10-13 21:12             ` Richard Cochran
2015-10-14  7:21             ` [Intel-wired-lan] " Thomas Gleixner
2015-10-14  7:21               ` Thomas Gleixner
2015-10-14  9:29               ` [Intel-wired-lan] " Richard Cochran
2015-10-14  9:29                 ` Richard Cochran
2015-10-14 14:22                 ` [Intel-wired-lan] " Thomas Gleixner
2015-10-14 14:22                   ` Thomas Gleixner
2015-10-14 16:18                   ` [Intel-wired-lan] " Richard Cochran
2015-10-14 16:18                     ` Richard Cochran
2015-10-15  2:34             ` [Intel-wired-lan] " Christopher Hall
2015-10-15  2:34               ` Christopher Hall
2015-10-15  5:41               ` [Intel-wired-lan] " Richard Cochran
2015-10-15  5:41                 ` Richard Cochran
2015-10-15  8:13                 ` [Intel-wired-lan] " Thomas Gleixner
2015-10-15  8:13                   ` Thomas Gleixner
2015-10-13  5:26   ` Richard Cochran [this message]
2015-10-13  5:26     ` Richard Cochran
2015-10-13 13:50   ` [Intel-wired-lan] " Richard Cochran
2015-10-13 13:50     ` Richard Cochran
2015-10-13 19:42   ` [Intel-wired-lan] " Thomas Gleixner
2015-10-13 19:42     ` Thomas Gleixner
2015-10-15  1:57     ` [Intel-wired-lan] " Christopher Hall
2015-10-15  1:57       ` Christopher Hall
2015-10-15  5:57       ` [Intel-wired-lan] " Richard Cochran
2015-10-15  5:57         ` Richard Cochran
2015-10-15  8:15       ` [Intel-wired-lan] " Thomas Gleixner
2015-10-15  8:15         ` Thomas Gleixner
2015-10-20  0:18         ` [Intel-wired-lan] " Christopher Hall
2015-10-20  0:18           ` Christopher Hall
2015-10-20  0:36           ` [Intel-wired-lan] " John Stultz
2015-10-20  0:36             ` John Stultz
2015-10-20  8:54             ` [Intel-wired-lan] " Richard Cochran
2015-10-20  8:54               ` Richard Cochran
2015-10-20 10:48               ` [Intel-wired-lan] " Thomas Gleixner
2015-10-20 10:48                 ` Thomas Gleixner
2015-10-20 11:51                 ` [Intel-wired-lan] " Richard Cochran
2015-10-20 11:51                   ` Richard Cochran
2015-10-20 14:55                   ` [Intel-wired-lan] " Richard Cochran
2015-10-20 14:55                     ` Richard Cochran
2015-10-20 19:11                     ` [Intel-wired-lan] " Thomas Gleixner
2015-10-20 19:11                       ` Thomas Gleixner
2015-10-20 19:36                       ` [Intel-wired-lan] " Richard Cochran
2015-10-20 19:36                         ` Richard Cochran
2015-10-20 20:16                       ` [Intel-wired-lan] " John Stultz
2015-10-20 20:16                         ` John Stultz
2015-10-21  7:44                         ` [Intel-wired-lan] " Thomas Gleixner
2015-10-21  7:44                           ` Thomas Gleixner
2015-11-03 19:18                           ` [Intel-wired-lan] " Stanton, Kevin B
2015-11-03 19:18                             ` Stanton, Kevin B
2015-11-09 21:17                             ` [Intel-wired-lan] " John Stultz
2015-11-09 21:17                               ` John Stultz
2015-10-12 18:45 ` [Intel-wired-lan] [PATCH v4 2/4] Always running timer " Christopher S. Hall
2015-10-12 18:45   ` Christopher S. Hall
2015-10-13  2:03   ` [Intel-wired-lan] " kbuild test robot
2015-10-13  2:03     ` kbuild test robot
2015-11-18 23:53   ` [Intel-wired-lan] " Jacob Pan
2015-11-18 23:53     ` Jacob Pan
2015-10-12 18:45 ` [Intel-wired-lan] [PATCH v4 3/4] Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping Christopher S. Hall
2015-10-12 18:45   ` Christopher S. Hall
2015-10-13 13:59   ` [Intel-wired-lan] " Richard Cochran
2015-10-13 13:59     ` Richard Cochran
2015-10-15  2:47     ` [Intel-wired-lan] " Christopher Hall
2015-10-15  2:47       ` Christopher Hall
2015-11-07  2:15     ` [Intel-wired-lan] " Christopher Hall
2015-11-07  2:15       ` Christopher Hall
2015-10-12 18:45 ` [Intel-wired-lan] [PATCH v4 4/4] Adds hardware supported cross timestamp Christopher S. Hall
2015-10-12 18:45   ` Christopher S. Hall
2015-10-13  2:10   ` [Intel-wired-lan] " kbuild test robot
2015-10-13  2:10     ` kbuild test robot
2015-10-13  2:11   ` [Intel-wired-lan] " kbuild test robot
2015-10-13  2:11     ` kbuild test robot
2015-10-13  2:31   ` [Intel-wired-lan] " David Miller
2015-10-13  2:31     ` David Miller

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=20151013052613.GB2437@netboy \
    --to=richardcochran@gmail.com \
    --cc=intel-wired-lan@osuosl.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.