Re: [Xen-devel] [PATCH] xsm/flask: Fix XSM support for HVMOP_track_dirty_vram

[Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>]

On 07/02/2013 06:03 AM, Aurelien Chartier wrote:
> This patch is intended for Xen 4.1 branch.
>
> The XSM check for HVMOP_track_dirty_vram is done with a call to xsm_hvm_param,
> therefore the switch handling that case should be located in flask_hvm_param
> and not in flask_hvmcontext.
>
> This was fixed upstream by the two following patches :
> * 875756ca34fabc7243c4a682ffd7008710a907e2 (add case in flask_hvm_param)
> * 652f94327383c5517b709f0a3e4b970216b3d375 (remove case from flask_hvmcontext)
>
> Signed-off-by: Aurelien Chartier <aurelien.chartier@xxxxxxxxxx>
Acked-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel