From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>, Jiri Olsa <jolsa@redhat.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [BUG] perf top: --stdio causes continuous refresh
Date: Thu, 6 Feb 2014 17:21:31 -0200 [thread overview]
Message-ID: <20140206192131.GA27665@infradead.org> (raw)
In-Reply-To: <52F3CAE3.7060007@gmail.com>
Em Thu, Feb 06, 2014 at 10:48:19AM -0700, David Ahern escreveu:
> On 2/6/14, 8:24 AM, Stephane Eranian wrote:
> >On Thu, Feb 6, 2014 at 3:09 PM, Arnaldo Carvalho de Melo
> >>>>I am using tip.git. Or try 3.11, 3.10.
> >>
> >>But my tests are on top of:
> >>
> >>[acme@ssdandy linux]$ uname -r
> >>3.11.4-101.fc18.x86_64
> >>
> >>I thought it was a 3.14ish one, building one to try there...
> >>
> >The kernel must be 3.14-rcX, the tool can be any version.
>
>
> I don't have time to do a git bisect, but I can narrow the window to
> 3.13-rc6 and 3.14-rc1. Just happened to update a server yesterday.
> perf-top --stdio runs fine on the former and shows the problem on
> the latter.
Humm,
/*
* Either timeout expired or we got an EINTR due to
* SIGWINCH, refresh screen in both cases.
*/
switch (poll(&stdin_poll, 1, delay_msecs)) {
And poll is returning 1:
951.068 ( 0.002 ms): poll(ufds: 0x7ff660befbb0, nfds: 1, timeout_msecs: 2000) = 1
Checking...
- Arnaldo
next prev parent reply other threads:[~2014-02-06 19:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 21:25 [BUG] perf top: --stdio causes continuous refresh Stephane Eranian
2014-02-05 23:12 ` Stephane Eranian
2014-02-06 13:56 ` Arnaldo Carvalho de Melo
2014-02-06 13:58 ` Stephane Eranian
2014-02-06 14:07 ` Arnaldo Carvalho de Melo
2014-02-06 14:09 ` Arnaldo Carvalho de Melo
2014-02-06 15:24 ` Stephane Eranian
2014-02-06 17:48 ` David Ahern
2014-02-06 19:21 ` Arnaldo Carvalho de Melo [this message]
2014-02-06 19:28 ` Arnaldo Carvalho de Melo
2014-02-06 20:21 ` Stephane Eranian
2014-02-10 21:03 ` Arnaldo Carvalho de Melo
2014-02-11 2:15 ` Peter Hurley
2014-02-11 12:14 ` Arnaldo Carvalho de Melo
2014-02-11 12:18 ` Peter Hurley
2014-02-11 16:49 ` [PATCH] n_tty: Fix poll() when TIME_CHAR and MIN_CHAR == 0 Peter Hurley
2014-02-11 18:31 ` David Ahern
2014-02-11 18:32 ` Eric Dumazet
2014-02-11 20:50 ` Arnaldo Carvalho de Melo
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=20140206192131.GA27665@infradead.org \
--to=acme@redhat.com \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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