From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: return value checking on multicalls
Date: Wed, 14 Mar 2007 10:02:54 -0700
Message-ID: <45F82ABE.4050103@goop.org>
References: <45F828EB.76E4.0078.0@novell.com> <45F82698.2050203@goop.org>
	<45F837AA.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45F837AA.76E4.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

Jan Beulich wrote:
> Hmm, that doesn't seem to fit all cases. There are hypercalls that
> return non-errno-like values, and you shouldn't make any
> assumptions about these.

It's been a nice simplification in my work, but I haven't used it with
anything where success > 0, or where I've even cared about results other
than failure.  And the advantage is that the incremental effort of
batching a series of calls is very small.

I just thought it might be useful.  Perhaps the interface could be
extended to be more useful in the cases you're looking at.

    J