From: Dan Aloni <dan@kernelim.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Bin Gao <bin.gao@linux.intel.com>
Subject: Re: TSC x86 fixes for LTS kernel 4.9.x
Date: Wed, 13 Dec 2017 11:45:20 +0200 [thread overview]
Message-ID: <20171213094520.GA23556@gmail.com> (raw)
In-Reply-To: <20171213090335.GA5496@kroah.com>
On Wed, Dec 13, 2017 at 10:03:35AM +0100, Greg KH wrote:
> On Wed, Dec 13, 2017 at 10:33:52AM +0200, Dan Aloni wrote:
> > Hi all,
> >
> > I've tested the following changes, belonging to merge commit f7dd3b1734e,
> > on top of 4.9.68 after a very easy backport from 4.10, and I think it
> > may be worthwhile adding them to 4.9.x:
> >
[..]
>
> I need git commit ids to be able to do anything :)
Sure, how about:
# git log 8c9b9d87b855 --oneline -n 19 --reverse --pretty="%h # %s" | awk -F" " '{print "git cherry-pick -x " $0}'
git cherry-pick -x 47c95a46d0fa # x86/tsc: Add X86_FEATURE_TSC_KNOWN_FREQ flag
git cherry-pick -x 4ca4df0b7eb0 # x86/tsc: Mark TSC frequency determined by CPUID as known
git cherry-pick -x 4635fdc696a8 # x86/tsc: Mark Intel ATOM_GOLDMONT TSC reliable
git cherry-pick -x f3a02ecebed7 # x86/tsc: Set TSC_KNOWN_FREQ and TSC_RELIABLE flags on Intel Atom SoCs
git cherry-pick -x 984fecebda3b # x86/tsc: Finalize the split of the TSC_RELIABLE flag
git cherry-pick -x 7b3d2f6e08ed # x86/tsc: Use X86_FEATURE_TSC_ADJUST in detect_art()
git cherry-pick -x bec8520dca0d # x86/tsc: Detect random warps
git cherry-pick -x 8b223bc7abe0 # x86/tsc: Store and check TSC ADJUST MSR
git cherry-pick -x 1d0095feea59 # x86/tsc: Verify TSC_ADJUST from idle
git cherry-pick -x a36f5136814b # x86/tsc: Sync test only for the first cpu in a package
git cherry-pick -x 4c5e3c637521 # x86/tsc: Move sync cleanup to a safe place
git cherry-pick -x 76d3b8515850 # x86/tsc: Prepare warp test for TSC adjustment
git cherry-pick -x cc4db26899dc # x86/tsc: Try to adjust TSC if sync test fails
git cherry-pick -x b836554386cc # x86/tsc: Fix broken CONFIG_X86_TSC=n build
git cherry-pick -x 31f8a651fc57 # x86/tsc: Validate cpumask pointer before accessing it
git cherry-pick -x 6a369583178d # x86/tsc: Validate TSC_ADJUST after resume
git cherry-pick -x 5bae156241e0 # x86/tsc: Force TSC_ADJUST register to value >= zero
git cherry-pick -x 16588f659257 # x86/tsc: Annotate printouts as firmware bug
git cherry-pick -x 8c9b9d87b855 # x86/tsc: Limit the adjust value further
There's a conflict only in a one small place in the first few patches.
> > These changes percisely fix an issue I am having with a relatively new
> > 8-core Intel(R) Core(TM) i7-7820X with an updated ASUS BIOS (December 2017).
> >
> > Under v4.9.68, the kernel fallbacks on the chosen clocksource to HPET which
> > just doesn't work - there is over a 200ms time drift that does not go
> > away even after repeated ntpdate sync attempts.
> >
> > For further testing I've posted a branch for these changes here:
> >
> > https://github.com/kernelim/linux tsc-fix-for-4.9.x
>
> Why not just use 4.14 instead? That's much easier than trying to use an
> old kernel like 4.9, right?
Yes, however the milage of 4.9.x seems more appealing somewhat.
I'll give 4.14.x a try mostly to see whether it solves hard locks that
I've seen with 4.13.x (all Fedora-based stable kernels) on three of my
machines -- an unrelated issue, and the main reason why I gave one of
the LTS branches a try.
--
Dan Aloni
next prev parent reply other threads:[~2017-12-13 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 8:33 TSC x86 fixes for LTS kernel 4.9.x Dan Aloni
2017-12-13 9:03 ` Greg KH
2017-12-13 9:45 ` Dan Aloni [this message]
2017-12-13 9:57 ` Greg KH
2017-12-13 10:14 ` Dan Aloni
2017-12-13 15:07 ` 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=20171213094520.GA23556@gmail.com \
--to=dan@kernelim.com \
--cc=bin.gao@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.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.