Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758558Ab3D2SUe (ORCPT ); Mon, 29 Apr 2013 14:20:34 -0400 Received: from oproxy7-pub.bluehost.com ([67.222.55.9]:52997 "HELO oproxy7-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1758437Ab3D2SUd (ORCPT ); Mon, 29 Apr 2013 14:20:33 -0400 Message-ID: <1367259631.8833.27.camel@Wailaba2> Subject: Re: [PATCH v2 1/3] process cputimer is moving faster than its corresponding clock From: Olivier Langlois To: KOSAKI Motohiro Cc: Peter Zijlstra , Ingo Molnar , Thomas Gleixner , schwidefsky@de.ibm.com, Steven Rostedt , Frederic Weisbecker , LKML Date: Mon, 29 Apr 2013 14:20:31 -0400 In-Reply-To: <517EB45D.60007@gmail.com> References: <1365184746.874.103.camel@Wailaba2> <1365593710.30071.52.camel@laptop> <1365608911.707.65.camel@Wailaba2> <1365763837.17140.52.camel@laptop> <1365782115.17140.68.camel@laptop> <1366951210.7911.28.camel@Wailaba2> <1366957639.7911.42.camel@Wailaba2> <517AD0AE.1030404@gmail.com> <1367037606.7911.66.camel@Wailaba2> <517DFFE9.4050808@gmail.com> <1367255407.8833.4.camel@Wailaba2> <517EB45D.60007@gmail.com> Organization: Trillion01 Inc Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.8.1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-Identified-User: {5686:box610.bluehost.com:olivierl:trillion01.com} {sentby:smtp auth 173.178.230.31 authed with olivier@trillion01.com} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1207 Lines: 31 > > >> I'm confused. glibc's rt/tst-cputimer1 doesn't have thread exiting code. I have > >> no seen any issue in this accounting. > > > > glibc launch a helper thread to receive timer signal and will also > > create a new thread upon signal reception when a timer is created with > > sigev_notify = SIGEV_THREAD; > > > > please see: > > > > glibc-2.17/nptl/sysdeps/unix/sysv/linux/timer_create.c > > glibc-2.17/nptl/sysdeps/unix/sysv/linux/timer_routines.c > > I know. I taled thread exiting. not thread creating. And, as far as I can see, only test sig1 can fail, > not thr[12]. > Apart from glibc helper thread, the threads created for handling timer firing all do exit immediatly as soon as user callback returns. I count 12 thread exits during tst-cputimer1 execution. The errors do add up hence you're more likely to see errors after 2.5 sec and up from start of execution. I have seen sig1, thr[12] fails. I see no reason why one could not fail. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/