Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752698Ab1BAQQh (ORCPT ); Tue, 1 Feb 2011 11:16:37 -0500 Received: from casper.infradead.org ([85.118.1.10]:32871 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751765Ab1BAQQh (ORCPT ); Tue, 1 Feb 2011 11:16:37 -0500 Subject: Re: [PATCH v2 4/6] KVM-GST: KVM Steal time registration From: Peter Zijlstra To: Glauber Costa Cc: Avi Kivity , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, aliguori@us.ibm.com, Rik van Riel , Jeremy Fitzhardinge , Venkatesh Pallipadi In-Reply-To: <1296575618.5081.13.camel@mothafucka.localdomain> References: <1296244340-15173-1-git-send-email-glommer@redhat.com> <1296244340-15173-5-git-send-email-glommer@redhat.com> <4D45649A.4090709@redhat.com> <1296575618.5081.13.camel@mothafucka.localdomain> Content-Type: text/plain; charset="UTF-8" Date: Tue, 01 Feb 2011 17:17:10 +0100 Message-ID: <1296577030.26581.236.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.30.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 912 Lines: 23 On Tue, 2011-02-01 at 13:53 -0200, Glauber Costa wrote: > > And since the granularity of the cpu accounting is too coarse, we end up > with much more steal time than we should, because things that are less > than 1 unity of cputime, are often rounded up to 1 unity of cputime. See, that! is the problem, don't round up like that. What you can do is: steal_ticks = steal_time_clock() / TICK_NSEC, or simply keep a steal time delta and every time it overflows cputime_one_jiffy insert a steal-time tick. Venki might have created some infrastructure for doing this with the IRQ_TIME accounting mess, but irqtime_account_process_tick() still gives me a head-ache. -- 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/