x86/HVM: don't use confusing/non-suitable XSM checks
authorJan Beulich <jbeulich@suse.com>
Tue, 20 May 2014 13:56:48 +0000 (15:56 +0200)
committerJan Beulich <jbeulich@suse.com>
Tue, 20 May 2014 13:56:48 +0000 (15:56 +0200)
commitcf37a923eae411d420f6519e6dcfd13e25cf276c
tree32b2545c43dfa87db61d8a4d988ad0f80c3b91d1
parentbac6334b51d9bcfe57ecf4a4cb5288348fcf044a
x86/HVM: don't use confusing/non-suitable XSM checks

XSM_TARGET checks following rcu_lock_{,live_}remote_domain_by_id() are
rather pointless and potentially confusing. Use XSM_DM_PRIV there
instead.

Note that setting flask_ops.hvm_control to flask_hvm_param() (instead
of introducing flask_hvm_control() is intentional - that function is
already separating the contol and non-control sub-operations.

Signed-off-by: Jan Beulich <jbeulich@suse.com>
Reviewed-by: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Acked-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
xen/arch/x86/hvm/hvm.c
xen/arch/x86/mm/mem_access.c
xen/arch/x86/mm/mem_event.c
xen/arch/x86/mm/mem_sharing.c
xen/include/xsm/dummy.h
xen/include/xsm/xsm.h
xen/xsm/dummy.c
xen/xsm/flask/hooks.c