From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/2] Paravirt loops per jiffy calculation Date: Sun, 27 Jul 2008 10:59:54 +0300 Message-ID: <488C2AFA.2030806@qumranet.com> References: <1216743328-3213-1-git-send-email-gcosta@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, glommer@gmail.com, aliguori@codemonkey.ws, mtosatti@redhat.com, virtualization@lists.linux-foundation.org To: Glauber Costa Return-path: Received: from il.qumranet.com ([212.179.150.194]:57246 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750926AbYG0H76 (ORCPT ); Sun, 27 Jul 2008 03:59:58 -0400 In-Reply-To: <1216743328-3213-1-git-send-email-gcosta@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Glauber Costa wrote: > Hey, > > Over the last weeks, there has been some discussion regarding paravirt > lpj calculation for kvm. Here's my shot at that. > > KVM hypervisor already put the right value in our pvclock structures, > as part of the xen compatibility efforts. > > So the first patch moves the respective xen code to pvclock.c (since > we'll be doing the same calculation anyway), while the second, implements > functions for kvm that makes use of it. > > Turns out that only implementing a pv get_tsc_khz is not enough, since > it will only do the right thing for cpu0, which is not what we desire. > > So we set preset_lpj. Recall this code is run before arch parameter setup, > so if we pass lpj=xx in the command line, it'll still work. > > Have a good (paravirtual) time! > > I only have this email out of the patchset. Please resend. -- error compiling committee.c: too many arguments to function