From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel De Graaf Subject: Re: [PATCH] xsm/flask: Fix XSM support for HVMOP_track_dirty_vram Date: Tue, 02 Jul 2013 10:54:56 -0400 Message-ID: <51D2E9C0.6010408@tycho.nsa.gov> References: <1372759416-5372-1-git-send-email-aurelien.chartier@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1372759416-5372-1-git-send-email-aurelien.chartier@citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Aurelien Chartier Cc: jbeulich@suse.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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 Acked-by: Daniel De Graaf