From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Andi Kleen <ak@linux.intel.com>,
Alexey Budankov <alexey.budankov@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Tvrtko Ursulin <tursulin@ursulin.net>,
linux-kernel@vger.kernel.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
"Rogozhkin, Dmitry V" <dmitry.v.rogozhkin@intel.com>
Subject: Re: [RFC] perf: Allow fine-grained PMU access control
Date: Mon, 11 Jun 2018 09:08:28 +0100 [thread overview]
Message-ID: <a2cb4e93-95c0-4a9f-db4d-69d6748c292e@linux.intel.com> (raw)
In-Reply-To: <20180522171925.GL4486@tassilo.jf.intel.com>
Hi,
On 22/05/2018 18:19, Andi Kleen wrote:
>> IMHO, it is unsafe for CBOX pmu but could IMC, UPI pmus be an exception here?
>> Because currently perf stat -I from IMC, UPI counters is only allowed when
>> system wide monitoring is permitted and this prevents joint perf record and
>> perf stat -I in cluster environments where users usually lack ability to
>> modify paranoid. Adding Andi who may have more ideas regarding all that.
>
> PMU isolation is about not making side channels worse. There are normally
> already side channels from timing, but it has a degree of noise.
>
> PMU isolation is just to prevent opening side channels with less noise.
> But reducing noise is always a trade off, it can never be perfect
> and at some point there are dimishing returns.
>
> In general the farther you are from the origin of the noise there
> is already more noise. The PMU can reduce the noise, but if it's far
> enough away it may not make much difference.
>
> So there are always trade offs with shades of grey, not a black
> and white situation. Depending on your security requirements
> it may be totally reasonable e.g. to allow the PMU
> on the memory controller (which is already very noisy in any case),
> but not on the caches.
>
> Or allow it only on the graphics which is already fairly isolated.
>
> So per pmu paranoid settings are a useful concept.
So it seems there is some positive feedback and fine-grained controls
would be useful for other PMU's in cluster environments.
If we have agreement on that, question is how to drive this forward?
Would someone be able to review the patch I've sent, or suggest more
people to look at it before it could be queued up for merge?
Regards,
Tvrtko
next prev parent reply other threads:[~2018-06-11 8:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 9:25 [RFC] perf: Allow fine-grained PMU access control Tvrtko Ursulin
2018-05-22 9:05 ` Peter Zijlstra
2018-05-22 9:29 ` Tvrtko Ursulin
2018-05-22 12:32 ` Peter Zijlstra
2018-05-22 13:01 ` Alexey Budankov
2018-05-22 17:19 ` Andi Kleen
2018-06-11 8:08 ` Tvrtko Ursulin [this message]
2018-06-18 8:06 ` Alexey Budankov
2018-05-22 16:15 ` Tvrtko Ursulin
-- strict thread matches above, loose matches on Subject: below --
2018-01-18 18:40 Tvrtko Ursulin
2018-01-19 16:45 ` Peter Zijlstra
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=a2cb4e93-95c0-4a9f-db4d-69d6748c292e@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=dmitry.v.rogozhkin@intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tursulin@ursulin.net \
--cc=tvrtko.ursulin@intel.com \
/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