All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ian Pratt" <m+Ian.Pratt@cl.cam.ac.uk>
To: Daniel Stekloff <dsteklof@us.ibm.com>
Cc: Kip Macy <kip.macy@gmail.com>,
	xen-devel@lists.xensource.com, Christian.Limpach@cl.cam.ac.uk
Subject: RE: DOM0_GETDOMAININFO intended behavior
Date: Wed, 8 Jun 2005 11:42:04 +0100	[thread overview]
Message-ID: <A95E2296287EAD4EB592B5DEEFCE0E9D282117@liverpoolst.ad.cl.cam.ac.uk> (raw)

> > Passing a flag in to explicitly request that you want to 
> iterate would 
> > probably be an improvement to the interface. 
> 
> Instead of changing the interface and the applications, how about the
> following: If you request a specific domain id and it doesn't 
> exist, you get back the expected result. If, however, you 
> want a list of domains it works like it has been.

Hmm, I'm not sure I like this. It turns a relatively minor 'gotcha' of
the hypervisor interface into something that's more confusing: if you're
trying to iterate over domains using xc_domain_getinfo then you have to
ask for at least two domains at a time otherwise you'll get ESRCH.

I think the cleanest fix is just to add an 'iterate' flag to the
parameters in GETDOMAININFO, no?

Ian

             reply	other threads:[~2005-06-08 10:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08 10:42 Ian Pratt [this message]
2005-06-09 22:35 ` DOM0_GETDOMAININFO intended behavior Daniel Stekloff
  -- strict thread matches above, loose matches on Subject: below --
2005-06-10  0:18 Macy, Kip
2005-06-04 21:51 Ian Pratt
2005-06-05  0:17 ` Kip Macy
2005-06-06 22:28 ` Daniel Stekloff
2005-06-04  8:20 Ian Pratt
2005-06-04 14:56 ` Daniel Stekloff
2005-06-04 19:42   ` Christian Limpach
2005-06-04 20:48     ` Daniel Stekloff
2005-06-03 23:18 Daniel Stekloff
2005-06-04  0:43 ` Kip Macy
2005-06-04  2:24   ` Anthony Liguori

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=A95E2296287EAD4EB592B5DEEFCE0E9D282117@liverpoolst.ad.cl.cam.ac.uk \
    --to=m+ian.pratt@cl.cam.ac.uk \
    --cc=Christian.Limpach@cl.cam.ac.uk \
    --cc=dsteklof@us.ibm.com \
    --cc=kip.macy@gmail.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.