From: Paul Bolle <pebolle@tiscali.nl>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Markus Trippelsdorf <markus@trippelsdorf.de>,
Mike Galbraith <umgwanakikbuti@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: perf samples too long without perf running (?!?)
Date: Sat, 08 Mar 2014 18:12:46 +0100 [thread overview]
Message-ID: <1394298766.2741.7.camel@x220> (raw)
In-Reply-To: <CALCETrW5Gpz7TYVVj2NxbKx4cFdePUQ1sEPDyLt5qLmy7KCycQ@mail.gmail.com>
On Sat, 2014-03-08 at 08:22 -0800, Andy Lutomirski wrote:
> Is it just me or is this whole situation screwed up for multiple reasons?
One minor reason would be that this message should read (say)
perf samples taking too long (2503 ns > 2500 ns), [...]
At least, that's what I thought after diving into the code to see what
was causing warnings like these.
And, since apparently things are just fine without administrator
intervention, I'd say another minor reason is that printing this at
KERN_INFO or KERN_NOTICE level should be enough here.
Paul Bolle
prev parent reply other threads:[~2014-03-08 17:12 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
2014-03-08 16:22 ` Andy Lutomirski
2014-03-08 17:12 ` Paul Bolle [this message]
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=1394298766.2741.7.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=markus@trippelsdorf.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox