From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "Shi, Yang" <yang.shi@linaro.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
linux-rt-users@vger.kernel.org
Subject: Re: -rt kernel just can show 8 perf events?
Date: Thu, 4 Feb 2016 16:16:23 +0100 [thread overview]
Message-ID: <20160204151623.GB3381@linutronix.de> (raw)
In-Reply-To: <566B0E72.50608@linaro.org>
* Shi, Yang | 2015-12-11 09:57:06 [-0800]:
>On 12/11/2015 9:36 AM, Sebastian Andrzej Siewior wrote:
>>And 4.1.12 (without -rt13) is not having this kind of problem?
>
>No. mainline 4.1.12 works well.
The same thing here. But I get this:
Performance counter stats for 'tar tJ':
144,407 cs
16,733 page-faults
16,732 minor-faults
1 major-faults
805,335 iTLB-load-misses (24.83%)
6,606,698 dTLB-load-misses (24.63%)
3,734,425,072 branches (37.35%)
228,660,856 L1-dcache-prefetches (37.06%)
4,564,273 L1-icache-prefetches (49.68%)
399,365,890 branch-misses # 10.69% of all branches (62.63%)
79,278,129 cache-misses (62.96%)
30,825,564,763 cycles (50.79%)
8.705696429 seconds time elapsed
once I apply this chunk:
diff --git a/kernel/events/core.c b/kernel/events/core.c
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -802,6 +802,7 @@ static void __perf_mux_hrtimer_init(struct perf_cpu_context *cpuctx, int cpu)
raw_spin_lock_init(&cpuctx->hrtimer_lock);
hrtimer_init(timer, CLOCK_MONOTONIC, HRTIMER_MODE_ABS_PINNED);
timer->function = perf_mux_hrtimer_handler;
+ timer->irqsafe = 1;
}
static int perf_mux_hrtimer_restart(struct perf_cpu_context *cpuctx)
>Yang
Sebastian
next prev parent reply other threads:[~2016-02-04 15:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 20:36 -rt kernel just can show 8 perf events? Shi, Yang
2015-12-11 17:36 ` Sebastian Andrzej Siewior
2015-12-11 17:57 ` Shi, Yang
2016-02-04 15:16 ` Sebastian Andrzej Siewior [this message]
2016-02-04 23:41 ` Shi, Yang
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=20160204151623.GB3381@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=acme@kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=yang.shi@linaro.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).