linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Raghavendra K T <raghavendra.kt@linux.vnet.ibm.com>
To: Rob Landley <rob@landley.net>
Cc: "H. Peter Anvin" <hpa@zytor.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: Mon, 04 Jun 2012 13:51:35 +0530	[thread overview]
Message-ID: <4FCC700F.8020609@linux.vnet.ibm.com> (raw)
In-Reply-To: <4FCC32F6.1010101@landley.net>

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
>


  reply	other threads:[~2012-06-04  8:22 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
2012-06-04  8:21     ` Raghavendra K T [this message]
  -- 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=4FCC700F.8020609@linux.vnet.ibm.com \
    --to=raghavendra.kt@linux.vnet.ibm.com \
    --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=rob@landley.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).