From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Dan Aloni <dan@kernelim.com>,
stable@vger.kernel.org,
Linux Kernel List <linux-kernel@vger.kernel.org>,
Bin Gao <bin.gao@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: TSC x86 fixes for LTS kernel 4.9.x
Date: Wed, 13 Dec 2017 16:07:12 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.20.1712131604230.1885@nanos> (raw)
In-Reply-To: <20171213095755.GA15957@kroah.com>
On Wed, 13 Dec 2017, Greg KH wrote:
> On Wed, Dec 13, 2017 at 11:45:20AM +0200, Dan Aloni wrote:
> > # 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.
>
> That's a lot of changes to be backported. I'm _really_ hesitant to do
> this, unless the maintainer of the code agrees it is ok...
Those TSC_ADJUST fixes are just an initial workaround. Peter has updated
that since then to the final and proper solution, which makes it dependend
on micro code version checks. If at all then the whole lot wants to be
backported, which is way more than the above set.
Thanks,
tglx
prev parent reply other threads:[~2017-12-13 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 8:33 Dan Aloni
2017-12-13 9:03 ` Greg KH
2017-12-13 9:45 ` Dan Aloni
2017-12-13 9:57 ` Greg KH
2017-12-13 10:14 ` Dan Aloni
2017-12-13 15:07 ` Thomas Gleixner [this message]
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=alpine.DEB.2.20.1712131604230.1885@nanos \
--to=tglx@linutronix.de \
--cc=bin.gao@linux.intel.com \
--cc=dan@kernelim.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.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®