From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: A few KVM security questions Date: Mon, 07 Dec 2009 16:09:48 +0200 Message-ID: <4B1D0CAC.7030005@redhat.com> References: <4B1CFD93.7090307@invisiblethingslab.com> <4B1D0057.8030707@redhat.com> <4B1D0383.1080306@invisiblethingslab.com> <4B1D0544.9000603@redhat.com> <4B1D0BFE.60202@invisiblethingslab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Joanna Rutkowska Return-path: Received: from mx1.redhat.com ([209.132.183.28]:27737 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935093AbZLGOJp (ORCPT ); Mon, 7 Dec 2009 09:09:45 -0500 In-Reply-To: <4B1D0BFE.60202@invisiblethingslab.com> Sender: kvm-owner@vger.kernel.org List-ID: On 12/07/2009 04:06 PM, Joanna Rutkowska wrote: > > Can you point to a document/source file that would list all the possible > interfaces between VM and the host? I.e. all the VMX handlers, and all > the hypercalls (PV interfaces). > arch/x86/kvm/vmx.c is the entry point for all interaction, but it quickly diverges. arch/x86/include/asm/kvm_para.h is the pv interface. -- error compiling committee.c: too many arguments to function