Em Wed, Apr 08, 2015 at 11:34:37AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Apr 08, 2015 at 11:14:27AM -0300, Arnaldo Carvalho de Melo escreveu:
> > Em Wed, Apr 08, 2015 at 07:48:23AM -0600, David Ahern escreveu:
> > > On 4/8/15 7:45 AM, Arnaldo Carvalho de Melo wrote:
> > > >>I also not
Em Wed, Apr 08, 2015 at 11:14:27AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Wed, Apr 08, 2015 at 07:48:23AM -0600, David Ahern escreveu:
> > On 4/8/15 7:45 AM, Arnaldo Carvalho de Melo wrote:
> > >>I also noticed that if I set /proc/sys/kernel/perf_event_paranoid to -1
> > >>to run it as !roo
Em Wed, Apr 08, 2015 at 07:48:23AM -0600, David Ahern escreveu:
> On 4/8/15 7:45 AM, Arnaldo Carvalho de Melo wrote:
> >>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
On 4/8/15 7:45 AM, Arnaldo Carvalho de Melo wrote:
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 t
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 unresponsiv
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
ca6c41c59b964d362823e80442
6 matches
Mail list logo
