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

[Xen-devel] return value checking on multicalls

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] return value checking on multicalls
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Wed, 14 Mar 2007 15:55:07 +0000
Delivery-date: Wed, 14 Mar 2007 08:53:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Many places currently don't even check HYPERVISOR_multicall()'s return
value, not to speak of checking the individual status codes. Would it be
acceptable to add an argument to this function to request to either fold
all status values into a global success code, or to force BUG_ON() each
individual status. Or should I rather add a new function with described
behavior? Or are there other suggestions?

Thanks, Jan

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

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