From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: 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 12:07:05 -0200 [thread overview]
Message-ID: <20140206140705.GB26955@infradead.org> (raw)
In-Reply-To: <CABPqkBS5qLDYyyv=n8fT4K+hA3uRWYmQOZmO+n-UE9=X=cEFzQ@mail.gmail.com>
Em Thu, Feb 06, 2014 at 02:58:01PM +0100, Stephane Eranian escreveu:
> On Thu, Feb 6, 2014 at 2:56 PM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > Em Wed, Feb 05, 2014 at 10:25:09PM +0100, Stephane Eranian escreveu:
> >> If you run perf top on 3.14 but you force --stdio mode, perf top
> >> goes crazy and constantly refreshes the output.
> >> It does that with many older versions of the perf as well on 3.14.
> >> It runs fine with newt mode.
> >> Works fine with my 3.11 kernel. So something must be broken
> >> with 3.14.
> >> Can you reproduce the problem as well?
> > Not so far, using my perf/urgent branch:
> I am using tip.git. Or try 3.11, 3.10.
Tried torvalds/master, no problem, looking at what the top's screen
refresh thread does we can see:
[root@ssdandy ~]# trace -t 3562 -e \!write
0.000 ( 0.000 ms): ... [continued]: poll()) = 0 Timeout
2031.522 (2002.480 ms): poll(ufds: 0x7fbb91596bb0, nfds: 1, timeout_msecs: 2000 ) = 0 Timeout
4064.346 (2002.456 ms): poll(ufds: 0x7fbb91596bb0, nfds: 1, timeout_msecs: 2000 ) = 0 Timeout
^C[root@ssdandy ~]#
I.e. waiting the default of:
.delay_secs = 2,
2 seconds between refreshes.
Checking out tip.tip, or are you suggesting to try an old perf binary, from
3.11 or 3.10 on top of a newer kernel?
- Arnaldo
next prev parent reply other threads:[~2014-02-06 14:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 21:25 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 [this message]
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
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=20140206140705.GB26955@infradead.org \
--to=acme@redhat.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
all inboxes | Powered by JetHome®