From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Re: [PATCH] xsm: Add support for HVMOP_track_dirty_vram. Date: Thu, 17 Nov 2011 09:15:35 +0000 Message-ID: References: <20111117060115.GA1901@spongy.cam.xci-test.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111117060115.GA1901@spongy.cam.xci-test.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jean Guyader , "xen-devel@lists.xensource.com" Cc: "jwcart2@tycho.nsa.gov" , Jean Guyader List-Id: xen-devel@lists.xenproject.org On 17/11/2011 06:01, "Jean Guyader" wrote: > 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 > > Can this patch go to 4.1 as well? Done. > Thanks, > Jean > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel