On Thu, Mar 9, 2017 at 9:56 AM, Jan Beulich <jbeul...@suse.com> wrote:
>>>> On 09.03.17 at 10:38, <rcojoc...@bitdefender.com> wrote:
>> @@ -4535,6 +4536,30 @@ static int do_altp2m_op(
>> a.u.set_mem_access.view);
>> break;
>>
>> + case HVMOP_altp2m_set_mem_access_multi:
>> + if ( a.u.set_mem_access_multi.pad ||
>> + a.u.set_mem_access_multi.opaque >= a.u.set_mem_access_multi.nr
>> )
>> + {
>> + rc = -EINVAL;
>> + break;
>> + }
>> + rc = p2m_set_mem_access_multi(d, a.u.set_mem_access_multi.pfn_list,
>> + a.u.set_mem_access_multi.access_list,
>> + a.u.set_mem_access_multi.nr,
>> + a.u.set_mem_access_multi.opaque,
>> + MEMOP_CMD_MASK,
>> + a.u.set_mem_access_multi.view);
>> + if ( rc > 0 )
>> + {
>> + a.u.set_mem_access_multi.opaque = rc;
>> + if ( __copy_to_guest(arg, &a, 1) )
>> + rc = -EFAULT;
>> + else
>> + rc = hypercall_create_continuation(__HYPERVISOR_hvm_op,
>> "lh",
>> + HVMOP_altp2m, arg);
>> + }
>> + break;
>
> Okay, so this is a hvmop, in which case I'm fine with the continuation
> model used.
>
> However - is this interface supposed to be usable by a guest on itself?
> Arguably the same question would apply to some of the other sub-ops
> too, but anyway.
>
AFAIK the only op the guest would use on itself is
HVMOP_altp2m_vcpu_enable_notify.
Tamas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
