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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
