linux-kernel - Re: [PATCH] Documentation/kvm : Add documentation on Hypercalls

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 04 Jun 2012 13:51:35 +0530
From:	Raghavendra K T <raghavendra.kt@...ux.vnet.ibm.com>
To:	Rob Landley <rob@...dley.net>
CC:	"H. Peter Anvin" <hpa@...or.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 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
>

--
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/