From: Peter Hurley <peter@hurleysoftware.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: David Ahern <dsahern@gmail.com>,
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: Tue, 11 Feb 2014 07:18:36 -0500 [thread overview]
Message-ID: <52FA151C.9040205@hurleysoftware.com> (raw)
In-Reply-To: <20140211121411.GA4368@infradead.org>
On 02/11/2014 07:14 AM, Arnaldo Carvalho de Melo wrote:
> Em Mon, Feb 10, 2014 at 09:15:42PM -0500, Peter Hurley escreveu:
>>> Bisected it down to:
>
>>> eb3e4668bd9e0bbda592e830e889f137e44ec9e4 is the first bad commit
>>> Author: Peter Hurley <peter@hurleysoftware.com>
>>> Date: Mon Dec 2 14:24:42 2013 -0500
>
>>> n_tty: Un-inline slow-path n_tty_receive_char()
>
>>> In a hurry now, will continue later, trying to understand what is the problem
>>> introduced by the above cset...
>
>>> Need to revert just this one to confirm that it is the culprit, etc.
>
>> Thanks for the report and bisect. Seems unlikely this commit is the
>> cause, but very likely to be some change I made since 3.13, since
>> I can repro on 3.14-rc1 but not on 3.13.2 -stable. I can also repro
>> this on 3.12 + the patch stack from me for 3.13 and 3.14.
>
>> I'm looking into this now.
>
> I just reverted just this cset and the problem persisted, so I'll wait
> for you on this one :-)
I did the same with the same result. So I'm re-bisecting on one machine
and tracing on another.
Regards,
Peter Hurley
next prev parent reply other threads:[~2014-02-11 12:18 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
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 [this message]
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=52FA151C.9040205@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=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