From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Mike Galbraith <umgwanakikbuti@gmail.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: perf samples too long without perf running (?!?)
Date: Sat, 8 Mar 2014 10:13:31 +0100 [thread overview]
Message-ID: <20140308091331.GA282@x4> (raw)
In-Reply-To: <1394265078.7215.11.camel@marge.simpson.net>
On 2014.03.08 at 08:51 +0100, Mike Galbraith wrote:
> On Fri, 2014-03-07 at 17:57 -0800, Andy Lutomirski wrote:
> > On recent (3.13) kernels, I'm frequently getting messages like:
> >
> > perf samples too long (2503 > 2500), lowering
> > kernel.perf_event_max_sample_rate to 50000
> >
> > a few seconds to minutes after bootup. As far as I know, I'm not
> > using perf. What's going on here?
>
> 14c63f17b1
>
> I get those all the time too, just building kernels.
I have:
echo 0 > /proc/sys/kernel/perf_cpu_time_max_percent
in my local startup script since that commit.
--
Markus
next prev parent reply other threads:[~2014-03-08 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 1:57 perf samples too long without perf running (?!?) Andy Lutomirski
2014-03-08 7:51 ` Mike Galbraith
2014-03-08 9:13 ` Markus Trippelsdorf [this message]
2014-03-08 16:22 ` Andy Lutomirski
2014-03-08 17:12 ` Paul Bolle
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=20140308091331.GA282@x4 \
--to=markus@trippelsdorf.de \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=umgwanakikbuti@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.