From: Borislav Petkov <bp@suse.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: torvalds@linux-foundation.org, jolsa@redhat.com,
vincent.weaver@maine.edu, alexander.shishkin@linux.intel.com,
linux-kernel@vger.kernel.org, mingo@kernel.org, acme@redhat.com,
tglx@linutronix.de, eranian@google.com, hpa@zytor.com,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf/core: Verify we have a single perf_hw_context PMU
Date: Mon, 4 Apr 2016 20:44:00 +0200 [thread overview]
Message-ID: <20160404184400.GB370@pd.tnic> (raw)
In-Reply-To: <20160404140208.GA3448@twins.programming.kicks-ass.net>
On Mon, Apr 04, 2016 at 04:02:08PM +0200, Peter Zijlstra wrote:
> This triggered on AMD machines..
>
> ---
> Subject: perf,amd: Do not register a task ctx for uncore PMUs
>
> Uncore PMUs are per node, they cannot have per-task counters.
>
> Reported-by: Borislav Petkov <bp@suse.de>
^
-and-tested-by: moi
> Reported-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> arch/x86/events/amd/uncore.c | 2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
...
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-04-04 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-26657848502b78474a5f17f9ce2ae6dc8d8d6262@git.kernel.org>
2016-04-04 14:02 ` Peter Zijlstra
2016-04-04 18:44 ` Borislav Petkov [this message]
2016-04-13 11:48 ` [tip:perf/core] perf/x86/amd/uncore: Do not register a task ctx for uncore PMUs tip-bot for 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=20160404184400.GB370@pd.tnic \
--to=bp@suse.de \
--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 \
--cc=vincent.weaver@maine.edu \
/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®