From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rob Landley Subject: Re: [PATCH] Documentation/kvm : Add documentation on Hypercalls Date: Sun, 03 Jun 2012 23:00:54 -0500 Message-ID: <4FCC32F6.1010101@landley.net> References: <20120531080116.24838.15692.sendpatchset@codeblue.in.ibm.com> <4FC7AE6C.9050106@zytor.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Raghavendra K T , 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: "H. Peter Anvin" Return-path: In-Reply-To: <4FC7AE6C.9050106@zytor.com> Sender: linux-doc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org 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), and hypercalls.txt is guest-side API for poking the host. How someone would write host-side code that _responds_ to a hypercall, I have no idea. (It goes in the host kernel?) Rob -- GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code. Either it's "mere aggregation", or a license violation. Pick one.