|
On 07/11 07:53, Jean Guyader wrote: > > 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@xxxxxxxxxxxxx> Can this patch go to 4.1 as well? Thanks, Jean _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Copyright
, Citrix Systems Inc. All rights reserved.
Legal and Privacy
|
