On Thu, 2015-04-02 at 12:26 +0200, Roger Pau Monne wrote:
> This is needed for performing save/restore of PV guests.
It's quite a big interface though, isn't it?
Could we restrict it to a subset of the operations perhaps? Or at least
justify here how it has been audited and found to be safe to allow an
HVM guest this access.
>
> Signed-off-by: Roger Pau Monné <roger....@citrix.com>
> Cc: Tim Deegan <t...@xen.org>
> Cc: Jan Beulich <jbeul...@suse.com>
> Cc: Andrew Cooper <andrew.coop...@citrix.com>
> ---
> xen/arch/x86/hvm/hvm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> index 3ff87c6..11680ba 100644
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -4907,6 +4907,7 @@ static hvm_hypercall_t *const
> pvh_hypercall64_table[NR_hypercalls] = {
> [ __HYPERVISOR_grant_table_op ] = (hvm_hypercall_t *)hvm_grant_table_op,
> HYPERCALL(vcpu_op),
> HYPERCALL(mmuext_op),
> + HYPERCALL(mmu_update),
> HYPERCALL(xsm_op),
> HYPERCALL(sched_op),
> HYPERCALL(event_channel_op),
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
