From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: Scheduling of VCPUs and allocation of Guest Physical Memory Date: Thu, 05 Jun 2008 07:54:29 -0500 Message-ID: <4847E205.4060605@codemonkey.ws> References: <484795C3.8030603@cse.iitb.ac.in> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Sukanto Ghosh Return-path: Received: from hs-out-0708.google.com ([64.233.178.249]:54730 "EHLO hs-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755915AbYFEMyo (ORCPT ); Thu, 5 Jun 2008 08:54:44 -0400 Received: by hs-out-0708.google.com with SMTP id 4so406025hsl.5 for ; Thu, 05 Jun 2008 05:54:43 -0700 (PDT) In-Reply-To: <484795C3.8030603@cse.iitb.ac.in> Sender: kvm-owner@vger.kernel.org List-ID: Sukanto Ghosh wrote: > Hi all, > > I have two questions regarding KVM: > > i) Is a VCPU scheduled like a normal Linux process A normal process. > or there is some mechanism by which performance guarantees can be > provided to the VCPUs ? FWIW, there are various mechanisms to do scheduler tuning in Linux. cpusets and cgroups both provide mechanisms to ensure "performance guarantees". > ii) Who does the allocation of host physical memory to the guest, is > it KVM module or the associated QEmu process ? The QEMU process allocates the memory via malloc(). > Also, I would be glad if you can provide me pointers to some > documentation/paper/literature which discusses KVM in greater detail > than what the paper "kvm: The Linux Virtual Machine Monitor" presents. The only other reference is the code itself. Regards, Anthony Liguori > Thanks, > Sukanto > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html