From: Vince Weaver <vincent.weaver@maine.edu>
To: vincent.weaver@maine.edu, mingo@kernel.org, eranian@google.com,
peterz@infradead.org, alexander.shishkin@linux.intel.com,
acme@redhat.com, hpa@zytor.com, torvalds@linux-foundation.org,
tglx@linutronix.de, linux-kernel@vger.kernel.org,
jolsa@redhat.com
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf/x86/intel: Force resched when TFA sysctl is modified
Date: Tue, 16 Apr 2019 12:28:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1904161227001.20764@macbook-air> (raw)
In-Reply-To: <tip-f447e4eb3ad1e60d173ca997fcb2ef2a66f12574@git.kernel.org>
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@google.com>
> AuthorDate: Mon, 8 Apr 2019 10:32:52 -0700
> Committer: Ingo Molnar <mingo@kernel.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? 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.
Vince
next prev parent reply other threads:[~2019-04-16 16:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 17:32 [PATCH v2 0/3] perf/x86/intel: force reschedule on TFA changes Stephane Eranian
2019-04-08 17:32 ` [PATCH v2 1/2] perf/core: add perf_ctx_resched() as global function Stephane Eranian
2019-04-15 15:45 ` Peter Zijlstra
2019-04-15 15:53 ` Peter Zijlstra
2019-04-16 11:33 ` [tip:perf/core] perf/core: Add perf_pmu_resched() " tip-bot for Stephane Eranian
2019-04-08 17:32 ` [PATCH v2 2/2] perf/x86/intel: force resched when TFA sysctl is modified Stephane Eranian
2019-04-15 15:57 ` Peter Zijlstra
2019-04-15 17:20 ` Stephane Eranian
2019-04-16 11:33 ` [tip:perf/core] perf/x86/intel: Force " tip-bot for Stephane Eranian
2019-04-16 16:28 ` Vince Weaver [this message]
2019-04-16 17:41 ` Peter Zijlstra
2019-04-17 6:06 ` Ingo Molnar
2019-04-18 21:50 ` Stephane Eranian
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.21.1904161227001.20764@macbook-air \
--to=vincent.weaver@maine.edu \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).