From: Rob Landley <rob@landley.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>, KVM <kvm@vger.kernel.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
Gleb Natapov <gleb@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Avi Kivity <avi@redhat.com>, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] Documentation/kvm : Add documentation on Hypercalls
Date: Sun, 03 Jun 2012 23:00:54 -0500 [thread overview]
Message-ID: <4FCC32F6.1010101@landley.net> (raw)
In-Reply-To: <4FC7AE6C.9050106@zytor.com>
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.
next prev parent reply other threads:[~2012-06-04 4:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 8:01 [PATCH] Documentation/kvm : Add documentation on Hypercalls Raghavendra K T
2012-05-31 17:44 ` Randy Dunlap
2012-05-31 18:55 ` Jan Kiszka
2012-05-31 18:59 ` H. Peter Anvin
2012-06-04 7:29 ` Raghavendra K T
2012-05-31 17:46 ` H. Peter Anvin
2012-06-04 4:00 ` Rob Landley [this message]
2012-06-04 8:21 ` Raghavendra K T
-- strict thread matches above, loose matches on Subject: below --
2012-07-24 8:53 Raghavendra K T
2012-07-24 12:13 ` Alexander Graf
2012-07-24 13:14 ` Raghavendra K T
2012-08-01 3:07 ` Marcelo Tosatti
2012-08-01 10:49 ` Raghavendra K T
2012-08-01 18:25 ` Marcelo Tosatti
2012-08-02 7:08 ` Raghavendra K T
2012-08-02 10:13 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FCC32F6.1010101@landley.net \
--to=rob@landley.net \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=hpa@zytor.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mtosatti@redhat.com \
--cc=raghavendra.kt@linux.vnet.ibm.com \
--cc=vatsa@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.