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: [Xen-changelog] [xen-unstable]vt-d: Fixpanic in msi_

To: Miroslav Rezanina <mrezanin@xxxxxxxxxx>
Subject: RE: [Xen-devel] RE: [Xen-changelog] [xen-unstable]vt-d: Fixpanic in msi_msg_read_remap_rte with acpi=off
From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date: Mon, 19 Oct 2009 16:49:35 +0800
Accept-language: zh-CN, en-US
Acceptlanguage: zh-CN, en-US
Cc: Keir, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 19 Oct 2009 01:50:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1079004822.361571255941269372.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <1949920474.361541255941211791.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <1079004822.361571255941269372.JavaMail.root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcpQlxMII5D1d3b9TUCLlsS85iHMjAAAKfyQ
Thread-topic: [Xen-devel] RE: [Xen-changelog] [xen-unstable]vt-d: Fixpanic in msi_msg_read_remap_rte with acpi=off
Miroslav Rezanina wrote:
> Hi Dexuan,
> you're right. We should print warning. In your patch, I do not
> understand 
> why you put comment only in setup_dom0_devices function. There is more
> calling of domain_context_mapping and we check NULL also in
In other places, the retuen value of domain_context_mapping() has been checked 
properly, e.g., passing to the caller, so we wouldn't ignore the failure. :-)

> domain_context_unmap and reassign_device_ownership. We should put
> warning in there too, shouldn't we? 
domain_context_unmap() is invoked in 2 places:
1) in intel_iommu_remove_device(), the return value has been propagated 
properly;
2) in reassign_device_ownership(), invoking reassign_device_ownership implies 
the device has been successfully assigned and the domain_context_mapping() 
returned success, so here the domain_context_unmap() can't fail.

The other returing place in reassign_device_ownership()  has been propagated 
properly to the caller.

Thanks,
-- Dexuan

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