[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190417060625.GB97541@gmail.com>
Date: Wed, 17 Apr 2019 08:06:25 +0200
From: Ingo Molnar <mingo@...nel.org>
To: Vince Weaver <vincent.weaver@...ne.edu>
Cc: eranian@...gle.com, peterz@...radead.org,
alexander.shishkin@...ux.intel.com, acme@...hat.com, hpa@...or.com,
torvalds@...ux-foundation.org, tglx@...utronix.de,
linux-kernel@...r.kernel.org, jolsa@...hat.com,
linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf/x86/intel: Force resched when TFA sysctl is
modified
* Vince Weaver <vincent.weaver@...ne.edu> wrote:
> On Tue, 16 Apr 2019, tip-bot for Stephane Eranian wrote:
>
> > Commit-ID: f447e4eb3ad1e60d173ca997fcb2ef2a66f12574
> > Gitweb: https://git.kernel.org/tip/f447e4eb3ad1e60d173ca997fcb2ef2a66f12574
> > Author: Stephane Eranian <eranian@...gle.com>
> > AuthorDate: Mon, 8 Apr 2019 10:32:52 -0700
> > Committer: Ingo Molnar <mingo@...nel.org>
> > CommitDate: Tue, 16 Apr 2019 12:19:35 +0200
> >
> > perf/x86/intel: Force resched when TFA sysctl is modified
>
> What's TFA? Tuna-fish-alarm?
Heh, I wish! :-)
> [...] Nowhere in the commit or in the code does it ever say what a TFA
> is or why we'd want to resched when it is modified.
Yeah, it's the TSX-Force-Abort acronym - Intel has numbed our general
dislike to random acrynyms ...
Peter and me usually fix such changelog context omissions, but this one
slipped through. :-/
The commit is too deep down perf/core already to rebase it just for the
changelog, but if we are going to rebase it for some functional reason
I'll take care of it next time around.
TFA. (Thanks For your Assistance. :-)
Ingo
Powered by blists - more mailing lists