From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Don Zickus <dzickus@redhat.com>, Jiri Olsa <jolsa@kernel.org>,
Joe Mario <jmario@redhat.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: BUG: perf top enters loop synthesizing events for existing threads
Date: Wed, 8 Apr 2015 10:45:45 -0300 [thread overview]
Message-ID: <20150408134545.GD5403@kernel.org> (raw)
In-Reply-To: <20150408134251.GC5403@kernel.org>
Em Wed, Apr 08, 2015 at 10:42:51AM -0300, Arnaldo Carvalho de Melo escreveu:
> Heads up,
>
> While testing some unrelated patches I noticed, in one of my
> machines, that 'perf top', as root, is entering some sort of loop and
> ends up consuming a lot of memory, making the system unresponsive,
> bisected it down to:
>
> [acme@zoo linux]$ git bisect good
> ca6c41c59b964d362823e80442e9e32c31106b29 is the first bad commit
> commit ca6c41c59b964d362823e80442e9e32c31106b29
> Author: David Ahern <dsahern@gmail.com>
> Date: Mon Mar 30 14:35:58 2015 -0600
>
> perf tools: Fix ppid for synthesized fork events
>
> 363b785f38 added synthesized fork events and set a thread's parent id to
> itself. Since we are already processing /proc/<pid>/status the ppid can
> be determined properly. Make it so.
>
> Signed-off-by: David Ahern <dsahern@gmail.com>
> Acked-by: Don Zickus <dzickus@redhat.com>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
> Cc: Joe Mario <jmario@redhat.com>
> Link: http://lkml.kernel.org/r/1427747758-18510-2-git-send-email-dsahern@gmail.com
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
>
> :040000 040000 24d479e4afbe95aaba882850473a870b6b3c7e87
> cc86fe0e51b5e8a66e8a23f934fd0c4ff0f8dcd6 M tools
> [acme@zoo linux]$
>
>
> I also noticed that if I set /proc/sys/kernel/perf_event_paranoid to -1
> to run it as !root, then the problem "goes away", which I think probably
> is explained by, as !root, not being able to parse some of the /proc
> files for existing threads and thus not triggering the bug, still
> investigating...
>
> I might need to revert it for this cycle...
Just reverting it makes the symptoms go away, to works as before. Trying
to understand the problem now.
- Arnaldo
next prev parent reply other threads:[~2015-04-08 13:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 13:42 BUG: perf top enters loop synthesizing events for existing threads Arnaldo Carvalho de Melo
2015-04-08 13:45 ` Arnaldo Carvalho de Melo [this message]
2015-04-08 13:48 ` David Ahern
2015-04-08 14:14 ` Arnaldo Carvalho de Melo
2015-04-08 14:34 ` Arnaldo Carvalho de Melo
2015-04-08 14:37 ` 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=20150408134545.GD5403@kernel.org \
--to=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=dzickus@redhat.com \
--cc=jmario@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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