xsm: Add support for HVMOP_track_dirty_vram.
authorJean Guyader <jean.guyader@eu.citrix.com>
Tue, 8 Nov 2011 19:41:47 +0000 (19:41 +0000)
committerJean Guyader <jean.guyader@eu.citrix.com>
Tue, 8 Nov 2011 19:41:47 +0000 (19:41 +0000)
commit35a5ddf29ab47c772b77e253131b3cb4757b6336
tree5fd5450b227d8d97b77661ce2bb697e9303f84ba
parent2b7ee729c5f89b24c107cca5b082453a855cdbf2
xsm: Add support for HVMOP_track_dirty_vram.

Xen try to inforce the xsm policy when a HVMOP_track_dirty_vram
is received (xen/arch/x86/hvm/hvm.c:3637). It was failing because
in flask_hvmcontext, xsm didn't have any case for this operation.

Signed-off-by: Jean Guyader <jean.guyader@eu.citrix.com>
Committed-by: Keir Fraser <keir@xen.org>
tools/flask/policy/policy/flask/access_vectors
tools/flask/policy/policy/modules/xen/xen.if
xen/xsm/flask/hooks.c
xen/xsm/flask/include/av_perm_to_string.h
xen/xsm/flask/include/av_permissions.h