Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030568AbXBFXXL (ORCPT ); Tue, 6 Feb 2007 18:23:11 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030567AbXBFXXL (ORCPT ); Tue, 6 Feb 2007 18:23:11 -0500 Received: from gw.goop.org ([64.81.55.164]:55862 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030563AbXBFXXJ (ORCPT ); Tue, 6 Feb 2007 18:23:09 -0500 Message-ID: <45C90DDA.3060009@goop.org> Date: Tue, 06 Feb 2007 15:23:06 -0800 From: Jeremy Fitzhardinge User-Agent: Thunderbird 1.5.0.9 (X11/20061219) MIME-Version: 1.0 To: Zachary Amsden CC: Andi Kleen , Linux Kernel Mailing List , Andrew Morton , Rusty Russell , Chris Wright Subject: Re: [PATCH 2/11] Sched clock paravirt op References: <200702060352.l163qeAf000727@zach-dev.vmware.com> <20070206123256.GF47229@muc.de> <45C9056A.8060504@vmware.com> In-Reply-To: <45C9056A.8060504@vmware.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 691 Lines: 15 Zachary Amsden wrote: > Scheduled (or available) time and real time are good notions. Stolen > time is debatable. But TSC is basically just always wrong. That's > why I don't want to overload the rdtsc operation. Well, in the Xen case it is actually guaranteed to be correct and useful as real time, but that's definitely not something we can expect in general. But you're talking specifically about schedulable vcpu time here, right? J - 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/