From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261621AbULBNt6 (ORCPT ); Thu, 2 Dec 2004 08:49:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261623AbULBNt6 (ORCPT ); Thu, 2 Dec 2004 08:49:58 -0500 Received: from mx2.elte.hu ([157.181.151.9]:60615 "EHLO mx2.elte.hu") by vger.kernel.org with ESMTP id S261621AbULBNtt (ORCPT ); Thu, 2 Dec 2004 08:49:49 -0500 Date: Thu, 2 Dec 2004 14:49:34 +0100 From: Ingo Molnar To: Florian Schmidt Cc: Rui Nuno Capela , linux-kernel@vger.kernel.org, Lee Revell , mark_h_johnson@raytheon.com, "K.R. Foley" , Bill Huey , Adam Heath , Thomas Gleixner , Michal Schmidt , Fernando Pablo Lopez-Lezcano , Karsten Wiese , Gunther Persoons , emann@mrv.com, Shane Shrybman , Amit Shah , Esben Nielsen , Andrew Morton Subject: Re: [patch] Real-Time Preemption, -RT-2.6.10-rc2-mm3-V0.7.31-19 Message-ID: <20041202134934.GA32216@elte.hu> References: <20041201213023.GA23470@elte.hu> <32788.192.168.1.8.1101938057.squirrel@192.168.1.8> <20041201220916.GA24992@elte.hu> <20041201234355.0dac74cf@mango.fruits.de> <20041202084040.GC7585@elte.hu> <20041202132218.02ea2c48@mango.fruits.de> <20041202122931.GA25357@elte.hu> <20041202140612.4c07bca8@mango.fruits.de> <20041202131002.GA30503@elte.hu> <20041202144037.5c9da188@mango.fruits.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041202144037.5c9da188@mango.fruits.de> User-Agent: Mutt/1.4.1i X-ELTE-SpamVersion: MailScanner 4.31.6-itk1 (ELTE 1.2) SpamAssassin 2.63 ClamAV 0.73 X-ELTE-VirusStatus: clean X-ELTE-SpamCheck: no X-ELTE-SpamCheck-Details: score=-4.9, required 5.9, autolearn=not spam, BAYES_00 -4.90 X-ELTE-SpamLevel: X-ELTE-SpamScore: -4 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org * Florian Schmidt wrote: > Ok, so if i want to find out whether a client violates the RT > constraints for its process callback i would have to add a call to > gettimeofday(1,1) at the start of the process callback and > gettimeofday(1,0) at the end. > > Everything which causes a reschedule inbetween will then cause SIGUSR2 > to be sent to the client for which i could either add a signal handler > in the client or just use gdb to get notified of it. correct. I'd expect there to be a number of less critical reschedules happening around startup/shutdown of a client, which one could consider a false positive, but there should be no unexpected rescheduling while the client is up and running. Ingo