From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932433AbXCNVec (ORCPT ); Wed, 14 Mar 2007 17:34:32 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933234AbXCNVec (ORCPT ); Wed, 14 Mar 2007 17:34:32 -0400 Received: from gateway-1237.mvista.com ([63.81.120.158]:51490 "EHLO gateway-1237.mvista.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932433AbXCNVeb (ORCPT ); Wed, 14 Mar 2007 17:34:31 -0400 Subject: Re: Stolen and degraded time and schedulers From: Daniel Walker To: Jeremy Fitzhardinge Cc: john stultz , Andi Kleen , Ingo Molnar , Thomas Gleixner , Con Kolivas , Rusty Russell , Zachary Amsden , James Morris , Chris Wright , Linux Kernel Mailing List , cpufreq@lists.linux.org.uk, Virtualization Mailing List , Peter Chubb In-Reply-To: <45F8663D.5050102@goop.org> References: <45F6D1D0.6080905@goop.org> <1173816769.22180.14.camel@localhost> <45F70A71.9090205@goop.org> <1173821224.1416.24.camel@dwalker1> <45F71EA5.2090203@goop.org> <1173837606.23595.32.camel@imap.mvista.com> <45F79B9C.20609@goop.org> <1173888673.3101.12.camel@imap.mvista.com> <45F824BE.1060708@goop.org> <1173891595.3101.17.camel@imap.mvista.com> <45F82C01.3000704@goop.org> <1173895607.3101.58.camel@imap.mvista.com> <45F841EE.6060703@goop.org> <1173898800.3101.81.camel@imap.mvista.com> <45F8508F.3070109@goop.org> <1173904438.3101.92.camel@imap.mvista.com> <45F8663D.5050102@goop.org> Content-Type: text/plain Date: Wed, 14 Mar 2007 14:34:25 -0700 Message-Id: <1173908065.3101.97.camel@imap.mvista.com> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 (2.8.2.1-3.fc6) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2007-03-14 at 14:16 -0700, Jeremy Fitzhardinge wrote: > > > It's also used for some posix cpu timers > > (sched_ns) , and it used for migration thread initialization. > > sched_ns doesn't use it directly except for the case where the process > is currently running. Anyway, it's compatible with what I'm talking about. It's used for measuring execution time, but timers are triggered based on that time, so it needs to be actual execution time. I don't know to what extent this is already inaccurate on some system tho. Daniel