From: Peter Zijlstra <peterz@infradead.org>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Subject: Re: perf: multiplexing broken on amd fam16h?
Date: Wed, 22 Jul 2015 17:41:47 +0200 [thread overview]
Message-ID: <20150722154147.GI18673@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150722150624.GV25159@twins.programming.kicks-ass.net>
On Wed, Jul 22, 2015 at 05:06:24PM +0200, Peter Zijlstra wrote:
> On Wed, Jul 22, 2015 at 11:02:21AM -0400, Vince Weaver wrote:
> > On Wed, 22 Jul 2015, Vince Weaver wrote:
> > >
> > > OK, so I have to admit I'm a bit weak on ftrace. What type of command
> > > line are you interested in seeing? The ones I've tried with trace-cmd
> > > have activated your trace_printks but there's 500MB of other data mixed
> > > in so maybe I am doing something wrong.
> >
> > maybe the "nop" plugin was what I wanted. I've posted the trace with that
> > here:
> >
> > http://web.eece.maine.edu/~vweaver/junk/jaguar.mpx.out.gz
>
> OK, that looks about right, lemme to stare at that.
Does this help?
---
kernel/events/core.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index d3dae3419b99..10d076b2572c 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -1868,8 +1868,6 @@ event_sched_in(struct perf_event *event,
perf_pmu_disable(event->pmu);
- event->tstamp_running += tstamp - event->tstamp_stopped;
-
perf_set_shadow_time(event, ctx, tstamp);
perf_log_itrace_start(event);
@@ -1881,6 +1879,8 @@ event_sched_in(struct perf_event *event,
goto out;
}
+ event->tstamp_running += tstamp - event->tstamp_stopped;
+
if (!is_software_event(event))
cpuctx->active_oncpu++;
if (!ctx->nr_active++)
next prev parent reply other threads:[~2015-07-22 15:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-21 18:14 Vince Weaver
2015-07-21 19:32 ` Peter Zijlstra
2015-07-21 20:08 ` Vince Weaver
2015-07-22 12:22 ` Peter Zijlstra
2015-07-22 14:57 ` Vince Weaver
2015-07-22 15:00 ` Peter Zijlstra
2015-07-22 15:02 ` Vince Weaver
2015-07-22 15:06 ` Peter Zijlstra
2015-07-22 15:41 ` Peter Zijlstra [this message]
2015-07-22 16:56 ` Vince Weaver
2015-07-22 19:07 ` Peter Zijlstra
2015-07-22 19:59 ` Vince Weaver
2015-07-22 20:10 ` Peter Zijlstra
2015-07-21 22:10 ` Peter Zijlstra
2015-07-22 14:10 ` Peter Zijlstra
2015-07-22 14:36 ` Vince Weaver
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=20150722154147.GI18673@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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
Powered by JetHome