[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FCC32F6.1010101@landley.net>
Date: Sun, 03 Jun 2012 23:00:54 -0500
From: Rob Landley <rob@...dley.net>
To: "H. Peter Anvin" <hpa@...or.com>
CC: Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com>,
linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
Srivatsa Vaddagiri <vatsa@...ux.vnet.ibm.com>,
Alexander Graf <agraf@...e.de>, KVM <kvm@...r.kernel.org>,
Marcelo Tosatti <mtosatti@...hat.com>,
Gleb Natapov <gleb@...hat.com>, Ingo Molnar <mingo@...hat.com>,
Avi Kivity <avi@...hat.com>,
Jan Kiszka <jan.kiszka@...mens.com>
Subject: Re: [PATCH] Documentation/kvm : Add documentation on Hypercalls
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 linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists