Alexander Graf <address@hidden> writes:
> Am 20.06.2013 um 17:42 schrieb Anthony Liguori
<address@hidden>:
>
>> Andreas Färber <address@hidden> 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?