[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1367027476.7911.60.camel@Wailaba2>
Date: Fri, 26 Apr 2013 21:51:16 -0400
From: Olivier Langlois <olivier@...llion01.com>
To: KOSAKI Motohiro <kosaki.motohiro@...il.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>, schwidefsky@...ibm.com,
Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] process cputimer is moving faster than its
corresponding clock
On Fri, 2013-04-26 at 15:08 -0400, KOSAKI Motohiro wrote:
> > I need to add that I can only confirm that to be true with
> > sum_exec_runtime.
> >
> > To affirm it to be true for stime and utime would require more
> > investigation. I didn't look them at all. I was only concerned with
> > sum_exec_runtime.
> >
> > I will prepare a v2 of the patch accounting all the feedbacks that I
> > received from KOSAKI Motohiro, Frederic Weisbecker and Peter Zijlstra
> > and send it back here for further discussion.
> >
> > Thank you very much all!
>
> Do you mean your utime test case still failure? If you share your test-case,
> I'm going to look at your issue too.
>
Sure with pleasure. My testcase is glibc-2.17/rt/tst-cputimer1.c
That being said, it strictly test CPUCLOCK_SCHED timers. Hence my focus
when modifying the code was strictly on sum_exec_runtime.
If utime and stime components of cputimer are moving faster than their
associated clock, this is something that I did not address.
--
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