From: "Christopher 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, "Andy Lutomirski" <luto@kernel.org>,
"Peter Zijlstra" <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
kevin.b.stanton@intel.com, kevin.j.clarke@intel.com
Subject: Re: [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource
Date: Mon, 22 Feb 2016 18:38:11 -0800 [thread overview]
Message-ID: <op.yc9llxxf1774gr@chall-mobl2.amr.corp.intel.com> (raw)
In-Reply-To: <56C63385.9050703@kernel.org>
On Thu, 18 Feb 2016 13:11:33 -0800, Andy Lutomirski <luto@kernel.org>
wrote:
>> +#define X86_FEATURE_INVARIANT_TSC (7*32+4) /* Intel Invariant TSC */
This is removed. It was basically an alias for NONSTOP_TSC and not needed.
>
>> +/*
>> + * Convert ART to TSC given numerator/denominator found in detect_art()
>> + */
>> +struct system_counterval_t convert_art_to_tsc(cycle_t art)
>> +{
>> + u64 tmp, res, rem;
>> +
>> + rem = do_div(art, art_to_tsc_denominator);
>> +
>> + res = art * art_to_tsc_numerator;
>> + tmp = rem * art_to_tsc_numerator;
>> +
>> + do_div(tmp, art_to_tsc_denominator);
>> + res += tmp;
>> +
>> + return (struct system_counterval_t) {.cs = art_related_clocksource,
>> + .cycles = res};
>
> The SDM and the patch description both mention an offset "k". Shouldn't
> this code at least have a comment about how it deals with the k != 0
> case?
I don't deal with the k != 0 case. I assume that IA32 TSC adjust MSR is 0
because it's almost always a *bad idea* to change it. I've discussed this
with a few other developers and there is some consensus agreeing. From an
earlier related thread Peter Zijlstra asserts that TSC adjust "had
better" be 0.(http://lkml.iu.edu/hypermail/linux/kernel/1507.3/03734.html).
Do we really need to accommodate BIOS's that do this?
Chris
next prev parent reply other threads:[~2016-02-23 2:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 20:25 [PATCH v7 0/8] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 1/8] time: Add cycles to nanoseconds translation Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 2/8] time: Add timekeeping snapshot code capturing system time and counter Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 3/8] time: Remove duplicated code in ktime_get_raw_and_real() Christopher S. Hall
2016-02-16 7:52 ` Richard Cochran
2016-02-16 18:23 ` Christopher Hall
2016-02-12 20:25 ` [PATCH v7 4/8] time: Add driver cross timestamp interface for higher precision time synchronization Christopher S. Hall
2016-02-16 7:56 ` Richard Cochran
2016-02-12 20:25 ` [PATCH v7 5/8] time: Add history to cross timestamp interface supporting slower devices Christopher S. Hall
2016-02-18 22:17 ` Richard Cochran
2016-02-19 17:33 ` John Stultz
2016-02-12 20:25 ` [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource Christopher S. Hall
2016-02-18 21:11 ` Andy Lutomirski
2016-02-23 2:38 ` Christopher Hall [this message]
2016-02-23 2:49 ` Andy Lutomirski
2016-02-12 20:25 ` [PATCH v7 7/8] ptp: Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping Christopher S. Hall
2016-02-12 20:25 ` [PATCH v7 8/8] net: e1000e: Adds hardware supported cross timestamp on e1000e nic Christopher S. Hall
2016-02-19 0:43 ` Jeff Kirsher
2016-02-18 19:26 ` [PATCH v7 0/8] Patchset enabling hardware based cross-timestamps for next gen Intel platforms John Stultz
2016-02-22 18:33 ` Christopher Hall
2016-02-22 18:49 ` John Stultz
2016-02-29 14:22 [PATCH v7 6/8] x86: tsc: Always Running Timer (ART) correlated clocksource Christopher S. Hall
2016-02-29 14:33 Christopher S. Hall
2016-03-02 1:11 ` Christopher Hall
2016-03-02 23:59 ` Christopher Hall
2016-03-03 0:34 ` Andy Lutomirski
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=op.yc9llxxf1774gr@chall-mobl2.amr.corp.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=kevin.j.clarke@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=peterz@infradead.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
Powered by JetHome