From: "Jan H. Schönherr" <jan@schnhrr.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: bp@alien8.de, mingo@redhat.com, x86@kernel.org,
pmenzel@molgen.mpg.de, Thomas.Lendacky@amd.com, hpa@zytor.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] x86/tsc: Allow quick PIT calibration despite interruptions
Date: Thu, 14 Feb 2019 22:48:35 +0100 [thread overview]
Message-ID: <993ab528-c06f-607c-438d-ec11b47427bf@schnhrr.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1902121257400.3710@nanos.tec.linutronix.de>
Am 12.02.19 um 12:57 schrieb Thomas Gleixner:
> On Tue, 29 Jan 2019, Thomas Gleixner wrote:
>> On Tue, 29 Jan 2019, Jan H. Schönherr wrote:
>>
>>> Am 29.01.2019 um 11:23 schrieb Jan H. Schönherr:
>>>> +calibrate:
>>>> + /*
>>>> + * Extrapolate the error and fail fast if the error will
>>>> + * never be below 500 ppm.
>>>> + */
>>>> + if (d1 + d1 >= (delta * MAX_QUICK_PIT_ITERATIONS) >> 11) {
>>>> + pr_info("Fast TSC calibration failed (wouldn't work)\n");
>>>> + return 0;
>>>> + }
>>>
>>> I messed this check up. "delta" is not the actual tsc delta between the
>>> first two successful reads at this point.
>>>
>>> (If it were, it might also correspond to more than one iteration; not
>>> sure if we care about that aspect, though.)
>>
>> I rather go for correct and if only for the reason that me/you/whoelse
>> doesn't have to scratch the head for an hour when looking at this half a
>> year from now.
>
> Any update on this?
Second version is out.
Regards
Jan
next prev parent reply other threads:[~2019-02-14 21:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-29 10:23 [PATCH 0/2] Fix TSC issues on (some) AMD Ryzen based systems Jan H. Schönherr
2019-01-29 10:23 ` [PATCH 1/2] x86/tsc: Allow quick PIT calibration despite interruptions Jan H. Schönherr
[not found] ` <5C50558B.8060405@schnhrr.de>
2019-01-29 22:28 ` Thomas Gleixner
2019-02-12 11:57 ` Thomas Gleixner
2019-02-14 21:48 ` Jan H. Schönherr [this message]
2019-01-29 10:23 ` [PATCH 2/2] cpu/hotplug: Unfreeze sibling CPU first on resume from S3 Jan H. Schönherr
2019-01-29 23:02 ` Thomas Gleixner
2019-01-29 19:33 ` [PATCH 0/2] Fix TSC issues on (some) AMD Ryzen based systems Paul Menzel
2019-01-29 19:37 ` Paul Menzel
2019-01-29 22:31 ` Thomas Gleixner
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=993ab528-c06f-607c-438d-ec11b47427bf@schnhrr.de \
--to=jan@schnhrr.de \
--cc=Thomas.Lendacky@amd.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--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
all inboxes | Powered by JetHome®