From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Scheduling of VCPUs and allocation of Guest Physical Memory Date: Wed, 18 Jun 2008 07:12:43 -0700 Message-ID: <485917DB.6080602@qumranet.com> References: <484795C3.8030603@cse.iitb.ac.in> <4847E205.4060605@codemonkey.ws> <4849483A.3030709@cse.iitb.ac.in> <48494C67.5090406@codemonkey.ws> <484D0F8F.4010807@cse.iitb.ac.in> <484D5808.9010907@qumranet.com> <4856775E.4050601@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 il.qumranet.com ([212.179.150.194]:38487 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754145AbYFROMw (ORCPT ); Wed, 18 Jun 2008 10:12:52 -0400 In-Reply-To: <4856775E.4050601@cse.iitb.ac.in> Sender: kvm-owner@vger.kernel.org List-ID: Sukanto Ghosh wrote: > I saw that KVM has guest SMP support upto 4 VCPUs. Are these VCPUs > modelled as threads of 'the process representing the VM' ? > Yes. > If it is, then, when a signal is sent to the that process by the QEMU > process, shouldn't all of the VCPUs (for that VM) exit to the userspace ? > You can send signals to a specific thread. > Who does this management of delivering the interrupt to the VCPU for > which it is intended for ? See qemu-kvm.c, look for pthread_kill(). > > > Also, while going through the KVM source, I found mention of opaque at > many places. What does 'opaque' refer to ? What is an opaque data ? It's a common C idiom letting a lower layer call back into the upper layer without knowing the upper layer's details. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.