All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: return value checking on multicalls
Date: Wed, 14 Mar 2007 10:02:54 -0700	[thread overview]
Message-ID: <45F82ABE.4050103@goop.org> (raw)
In-Reply-To: <45F837AA.76E4.0078.0@novell.com>

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

      reply	other threads:[~2007-03-14 17:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 15:55 return value checking on multicalls Jan Beulich
2007-03-14 16:00 ` Keir Fraser
2007-03-14 16:45 ` Jeremy Fitzhardinge
2007-03-14 16:58   ` Jan Beulich
2007-03-14 17:02     ` Jeremy Fitzhardinge [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45F82ABE.4050103@goop.org \
    --to=jeremy@goop.org \
    --cc=jbeulich@novell.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.