From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <4CE2CFDC.4070402@goop.org> Date: Tue, 16 Nov 2010 10:39:24 -0800 From: Jeremy Fitzhardinge MIME-Version: 1.0 Subject: Re: [RFC][PATCH v2 4/7] taskstats: Add per task steal time accounting References: <20101111170352.732381138@linux.vnet.ibm.com> <20101111170815.024542355@linux.vnet.ibm.com> <1289677083.2109.167.camel@laptop> <20101115155057.15f3be35@mschwide.boeblingen.de.ibm.com> <1289833883.2109.494.camel@laptop> <20101115184206.4463fd05@mschwide.boeblingen.de.ibm.com> <1289843441.2109.520.camel@laptop> <20101115185923.1c353d07@mschwide.boeblingen.de.ibm.com> <1289844524.2109.524.camel@laptop> <20101116095101.5d86d1e5@mschwide.boeblingen.de.ibm.com> <1289909768.2109.592.camel@laptop> <20101116163325.755a709f@mschwide.boeblingen.de.ibm.com> <1289922329.2109.627.camel@laptop> <20101116170549.05d9e5c6@mschwide.boeblingen.de.ibm.com> In-Reply-To: <20101116170549.05d9e5c6@mschwide.boeblingen.de.ibm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-Archive: List-Post: To: Martin Schwidefsky Cc: Peter Zijlstra , Michael Holzheu , Shailabh Nagar , Andrew Morton , Venkatesh Pallipadi , Suresh Siddha , Ingo Molnar , Oleg Nesterov , John stultz , Thomas Gleixner , Balbir Singh , Heiko Carstens , Roland McGrath , "linux-kernel@vger.kernel.org" , "linux-s390@vger.kernel.org" , Avi Kivity List-ID: On 11/16/2010 08:05 AM, Martin Schwidefsky wrote: >>> Yes and no. The tracepoint idea looks interesting in itself. But that does >>> not completely replace the per-task steal time. The hypervisor can take >>> away the cpu anytime, it is still interesting to know which task was hit >>> hardest by that. You could view the cpu time lost by a hypercall as >>> "synchronous" steal time for the task, the remaining delta to the total >>> per-task steal time as "asynchronous" steal time. >> Right, so there is no way the guest knows about the vcpu getting >> scheduled, it can only derive the fact from hardware clocks after the >> fact? > Correct. Yes, same for Xen. J