From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Gleb Natapov <gleb@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH RFC] perf, core: disable pmu while context rotation only if needed
Date: Tue, 15 Nov 2011 13:55:18 +0100 [thread overview]
Message-ID: <1321361719.1421.67.camel@twins> (raw)
In-Reply-To: <20111115123814.GE3225@redhat.com>
On Tue, 2011-11-15 at 14:38 +0200, Gleb Natapov wrote:
> On Tue, Nov 15, 2011 at 01:07:13PM +0100, Peter Zijlstra wrote:
> > On Tue, 2011-11-15 at 13:34 +0200, Gleb Natapov wrote:
> > >
> > > Currently pmu is disabled and re-enabled on each timer interrupt even
> > > when no rotation or frequency adjustment is needed. On Intel CPU this
> > > results in two writes into PERF_GLOBAL_CTRL MSR per tick. On bare metal
> > > it does not cause significant slowdown, but when running perf in a virtual
> > > machine it leads to 20% slowdown on my machine.
> >
> >
> > I detest asymmetric locking like that, does something like the below
> > also work for you?
> >
> It does.
ok, great.
> >
> > + if (!rotate && !freq)
> > + goto done;
> > +
> > perf_ctx_lock(cpuctx, cpuctx->task_ctx);
> > perf_pmu_disable(cpuctx->ctx.pmu);
> > +
> > + if (!freq)
> > + goto rotate;
> > +
> Why goto, why not
>
> if (freq) {
> > perf_ctx_adjust_freq(&cpuctx->ctx, interval);
> > if (ctx)
> > perf_ctx_adjust_freq(ctx, interval);
> }
>
> And the same with next goto.
Because, uhm,. dunno. Let me make that if()s and commit the thing.
Thanks!
next prev parent reply other threads:[~2011-11-15 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 11:34 [PATCH RFC] perf, core: disable pmu while context rotation only if needed Gleb Natapov
2011-11-15 12:07 ` Peter Zijlstra
2011-11-15 12:38 ` Gleb Natapov
2011-11-15 12:55 ` Peter Zijlstra [this message]
2011-11-22 10:56 ` Gleb Natapov
2011-11-22 10:59 ` 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=1321361719.1421.67.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=gleb@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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