[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111015170452.GD29782@elte.hu>
Date: Sat, 15 Oct 2011 19:04:52 +0200
From: Ingo Molnar <mingo@...e.hu>
To: David Ahern <dsahern@...il.com>
Cc: Arnaldo Carvalho de Melo <acme@...radead.org>,
linux-kernel@...r.kernel.org,
Frederic Weisbecker <fweisbec@...il.com>,
Mike Galbraith <efault@....de>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <peterz@...radead.org>,
Stephane Eranian <eranian@...gle.com>,
Thomas Jarosch <thomas.jarosch@...ra2net.com>,
arnaldo.melo@...il.com
Subject: Re: [GIT PULL 0/5] perf/core improvements and fixes
* David Ahern <dsahern@...il.com> wrote:
> On 10/15/2011 08:59 AM, Ingo Molnar wrote:
> > Btw., i noticed another weirdness - sometimes after startup i get
> > this message:
> >
> > /lib64/libc-2.14.90.so was updated, restart the long running apps that use it!
> >
> > but it was not updated recently:
> >
> > earth5:~/tip/tools/perf> ll /lib64/libc-2.14.90.so
> > -rwxr-xr-x 1 root root 2062920 Sep 28 15:11 /lib64/libc-2.14.90.so
> > earth5:~/tip/tools/perf> date
> > Sat Oct 15 16:59:04 CEST 2011
> > earth5:~/tip/tools/perf> uptime
> > 16:59:08 up 19 days, 21:35, 11 users, load average: 7.77, 7.48, 3.81
>
> I got the impression that comment was relative to when the
> processes were started versus prelink touching it. In your case the
> mod time of libc is after the uptime of the box.
Ok, that makes sense. Do we report this in perf report output as
well?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists