From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Counting VCPU instructions Date: Tue, 13 Jan 2009 22:04:42 +0200 Message-ID: <496CF3DA.4010207@redhat.com> References: <419eef1d0901121122w4e14a2clf2cc2ddb1adcb3fb@mail.gmail.com> <496C5F22.1020706@redhat.com> <419eef1d0901130936sf82bceesf3f5c2f27ca6a251@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm-devel To: Abhishek Saksena Return-path: Received: from mx2.redhat.com ([66.187.237.31]:48078 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752751AbZAMUEs (ORCPT ); Tue, 13 Jan 2009 15:04:48 -0500 In-Reply-To: <419eef1d0901130936sf82bceesf3f5c2f27ca6a251@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: (restoring cc) Abhishek Saksena wrote: >>> Other thing which I am not sure how KVM kerenel is synconrinized with >>> Qemu kernel? Can somebody explain this? >>> >>> >> What's the qemu kernel? >> > > Just qemu. Qemu has it's own timers how they are synced up with KVM? > For example if the guest is getting too far ahead, we need to slow it down. > Guest getting too far ahead of what? Why would we want to slow down a guest? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.