netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher S. Hall" <christopher.s.hall@intel.com>
To: tglx@linutronix.de, richardcochran@gmail.com, mingo@redhat.com,
	john.stultz@linaro.org, hpa@zytor.com,
	jeffrey.t.kirsher@intel.com
Cc: "Christopher S. Hall" <christopher.s.hall@intel.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
	kevin.b.stanton@intel.com
Subject: [PATCH v6 3/9] Add correlated clocksource relating aliased auxiliary and system clocks
Date: Wed, 13 Jan 2016 04:12:23 -0800	[thread overview]
Message-ID: <1452687149-11281-4-git-send-email-christopher.s.hall@intel.com> (raw)
In-Reply-To: <1452687149-11281-1-git-send-email-christopher.s.hall@intel.com>

ACKNOWLEDGMENT: The original correlated clock source and cross
timestamp code was developed by Thomas Gleixner
<tglx@linutronix.de>. It has changed considerably and any mistakes are
mine.

The timekeeping and clocksource code don't currently comprehend two
clocks that are aliases of one another. That is clocks that are
*exactly* related. The correlated_cs struct encapsulated this
relationship between a clocksource and its alias clock. Modern Intel
hardware provides an Always Running Timer (ART) which is exactly
related to TSC through a known frequency ratio. The ART is an example
of a correlated clocksource.

Signed-off-by: Christopher S. Hall <christopher.s.hall@intel.com>
---
 include/linux/clocksource.h | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/include/linux/clocksource.h b/include/linux/clocksource.h
index 4542293..726ca68 100644
--- a/include/linux/clocksource.h
+++ b/include/linux/clocksource.h
@@ -267,4 +267,18 @@ struct system_counterval_t {
 	struct clocksource	*cs;
 };
 
+/*
+ * struct correlated_cs - Descriptor for a clocksource correlated to another
+ *	clocksource
+ * @related_cs:		Pointer to the related timekeeping clocksource
+ * @convert:		Conversion function to convert a timestamp from
+ *			the correlated clocksource to cycles of the related
+ *			timekeeping clocksource
+ */
+struct correlated_cs {
+	struct clocksource	*related_cs;
+	cycle_t			(*convert)(struct correlated_cs *cs,
+					   cycle_t cycles);
+};
+
 #endif /* _LINUX_CLOCKSOURCE_H */
-- 
2.1.4

  parent reply	other threads:[~2016-01-13 12:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-13 12:12 [PATCH v6 0/9] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2016-01-13 12:12 ` [PATCH v6 1/9] Add cycles to nanoseconds translation Christopher S. Hall
2016-01-13 12:12 ` [PATCH v6 2/9] Add driver cross timestamp interface for higher precision time synchronization Christopher S. Hall
2016-01-13 21:30   ` Richard Cochran
2016-01-13 12:12 ` Christopher S. Hall [this message]
2016-01-15  0:24   ` [PATCH v6 3/9] Add correlated clocksource relating aliased auxiliary and system clocks John Stultz
2016-01-15 10:29     ` Thomas Gleixner
2016-01-13 12:12 ` [PATCH v6 4/9] Always Running Timer (ART) correlated clocksource Christopher S. Hall
2016-01-14 22:00   ` John Stultz
2016-01-13 12:12 ` [PATCH v6 5/9] Add timekeeping snapshot code capturing system time and counter Christopher S. Hall
2016-01-13 12:12 ` [PATCH v6 6/9] Add history to cross timestamp interface supporting slower devices Christopher S. Hall
2016-01-13 12:12 ` [PATCH v6 7/9] Remove duplicated code in ktime_get_raw_and_real() Christopher S. Hall
2016-01-13 12:12 ` [PATCH v6 8/9] Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping Christopher S. Hall
2016-01-13 21:31   ` Richard Cochran
2016-01-13 12:12 ` [PATCH v6 9/9] Adds hardware supported cross timestamp Christopher S. Hall
2016-01-15  0:49 ` [PATCH v6 0/9] Patchset enabling hardware based cross-timestamps for next gen Intel platforms John Stultz

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=1452687149-11281-4-git-send-email-christopher.s.hall@intel.com \
    --to=christopher.s.hall@intel.com \
    --cc=hpa@zytor.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=john.stultz@linaro.org \
    --cc=kevin.b.stanton@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).