On 06/20/2013 01:58:55 PM, Anthony Liguori wrote:
Alexander Graf <ag...@suse.de> writes:
> Am 20.06.2013 um 17:42 schrieb Anthony Liguori
<aligu...@us.ibm.com>:
>
>> Andreas Färber <afaer...@suse.de> writes:
>>
>>> The functions are called spapr_hcall*() but the protocol uses
>>> papr_hypercall?
>>
>> The discrepancy is inherited in the KVM vs. QEMU interfaces. It's
>> called papr_hypercall in the KVM interface vs. spapr in QEMU.
>>
>> I honestly don't know what the distinction between spapr and papr
is.
>
> PAPR is what PAPR calls itself. However, there is also an ePAPR for
> BookE, so in order to distinguish the 2 more easily, we named the
> server version spapr wherever we remembered to.
So does it make sense to have papr_hypercall()? Do hypercalls exist
with the virtualization extensions on BookE?
Yes, there are hypercalls on booke. Currently the few that KVM
supports are all handled in the kernel, but that may change, especially
since Alex is thinking about new hypercalls for guest reset/stop.
-Scott
