WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: [PATCH] xsm: Add support for HVMOP_track_dirty_vram.

To: Jean Guyader <jean.guyader@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] xsm: Add support for HVMOP_track_dirty_vram.
From: Keir Fraser <keir@xxxxxxx>
Date: Thu, 17 Nov 2011 09:15:35 +0000
Cc: "jwcart2@xxxxxxxxxxxxx" <jwcart2@xxxxxxxxxxxxx>, Jean Guyader <Jean.Guyader@xxxxxxxxxx>
Delivery-date: Thu, 17 Nov 2011 01:16:17 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=yi1Q/HLa6jUIie1hSTwmuhX8wVtrVHyTWCHlnMaxIVc=; b=mCh7LfeCPwG4zE8cDEOwnP8Rlgw/en0qQq1INioC9cOf7dRP195PcHUvGR1TM4QQHo WiuuoiVVmSKEGw+eVCd3WKzP1p6+vsEgpKC9A+1Kph3GEShhiLHdXhhc3jae6iPnzVFS 7eqELM/n2+N9usVIP6pSebYRJz/mkM/06i9TQ=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20111117060115.GA1901@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcylCXaavltQN47KukmxgX19MbDw5g==
Thread-topic: [Xen-devel] Re: [PATCH] xsm: Add support for HVMOP_track_dirty_vram.
User-agent: Microsoft-Entourage/12.31.0.110725
On 17/11/2011 06:01, "Jean Guyader" <jean.guyader@xxxxxxxxxxxxx> 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 <jean.guyader@xxxxxxxxxxxxx>
> 
> Can this patch go to 4.1 as well?

Done.

> Thanks,
> Jean
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>