From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 29 Jun 2007 17:29:07 +0200 From: Daniel Simon Message-ID: <20070629172907.698f9586@domain.hid> In-Reply-To: <46851E97.7030402@domain.hid> References: <2404.194.199.21.225.1181233422.squirrel@domain.hid> <4668440F.7020706@domain.hid> <20070608124927.1b789a9e@domain.hid> <46693B6B.1010201@domain.hid> <20070625175107.438849fa@domain.hid> <467FF391.8020401@domain.hid> <20070627105726.7db7a459@domain.hid> <46825054.7030800@domain.hid> <20070629164326.15579570@domain.hid> <46851E97.7030402@domain.hid> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-core] measuring tasks execution time List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: xenomai-core On Fri, 29 Jun 2007 17:00:39 +0200 Jan Kiszka wrote: > Exectime is only updated on task switches. So you are not obtaining the true > value when requesting your own data. Use the same formula for both cases. yes, but like that the fraction of time spent in the current execution is not accounted, which might be sometimes useful (e.g. to integrate the cost of a feedback scheduler in the total control budget) another potentially useful feature would be also accounting the execution time spent in secondary mode... no idea on how to do that. BTW, Posix defines an optional CLOCK_THREAD_CPUTIME which is assumed to provide this measure ? Daniel -- Daniel SIMON Projet NeCS INRIA Rhone-Alpes Inovallee, 655 avenue de l'Europe, Montbonnot 38 334 Saint Ismier Cedex France Daniel.Simon@domain.hid Phone:(33)476615328 Fax:(33)476615252 http://necs.inrialpes.fr/people/simon/