From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raghavendra K T Subject: Re: [PATCH] Documentation/kvm : Add documentation on Hypercalls Date: Mon, 04 Jun 2012 13:51:35 +0530 Message-ID: <4FCC700F.8020609@linux.vnet.ibm.com> References: <20120531080116.24838.15692.sendpatchset@codeblue.in.ibm.com> <4FC7AE6C.9050106@zytor.com> <4FCC32F6.1010101@landley.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "H. Peter Anvin" , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, Srivatsa Vaddagiri , Alexander Graf , KVM , Marcelo Tosatti , Gleb Natapov , Ingo Molnar , Avi Kivity , Jan Kiszka To: Rob Landley Return-path: In-Reply-To: <4FCC32F6.1010101@landley.net> Sender: linux-doc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 06/04/2012 09:30 AM, Rob Landley wrote: > On 05/31/2012 12:46 PM, H. Peter Anvin wrote: >> On 05/31/2012 01:01 AM, Raghavendra K T wrote: >>> + >>> +TODO: >>> +1. more information on input and output needed? >>> +2. Add more detail to purpose of hypercalls. >>> >> >> 1. definitely, including the hypercall ABI. >> >> -hpa >> > > I was wondering about that. It looks like > Documentation/virtual/kvm/api.txt might cover some of that already in > section 5, but it doesn't look complete... > > Also, could I get a 00-INDEX file for this directory explaining what > these individual files are? I think "api.txt" is supposed to be > host-side API for controlling a guest VM (from userspace via ioctls, > looks like), api.txt has plenty of information apart from features which are related to guest side api (generally controls / knows PV features available, that may also involve host query of guest cpuid). and capability (of) related to host. and hypercalls.txt is guest-side API for poking the host. hypercall can be used to take some actions (as needed by guest / exchange information) > How someone would write host-side code that _responds_ to a hypercall, I > have no idea. (It goes in the host kernel?) > > Rob >