All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Stekloff <dsteklof@us.ibm.com>
To: xen-devel@lists.xensource.com
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, Kip Macy <kip.macy@gmail.com>
Subject: Re: DOM0_GETDOMAININFO intended behavior
Date: Sat, 4 Jun 2005 07:56:26 -0700	[thread overview]
Message-ID: <200506040756.26647.dsteklof@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D28206E@liverpoolst.ad.cl.cam.ac.uk>

On Saturday 04 June 2005 01:20, Ian Pratt wrote:
> > :-)
> >
> > I asked the same question a week or two ago and yes it is
> > intended. It provides for easy iteration. I think it is kind
> > of a hackish interface as it isn't uniform with *all* the
> > other DOM0 calls. However, it works and once you know to
> > check the domid return value your code will work as expected.
>
> I suppose we could add a flag to indicate whether you were iterating or
> wanted information on a specific domain. I think currently the only case
> where we want to iterate is 'xm list'.


If you're ok with changing the interface, wouldn't it be better for the 
hypercall to get and return just the requested domain info while you move the 
interation to libxc? The library could have two calls, one which calls the 
other: xc_domain_getinfo() and xc_domain_getinfo_list()

This way you'd have a hypercall that returns expected information and you 
wouldn't have to worry about flags. 

Thanks,

Dan

  reply	other threads:[~2005-06-04 14:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-04  8:20 DOM0_GETDOMAININFO intended behavior Ian Pratt
2005-06-04 14:56 ` Daniel Stekloff [this message]
2005-06-04 19:42   ` Christian Limpach
2005-06-04 20:48     ` Daniel Stekloff
  -- strict thread matches above, loose matches on Subject: below --
2005-06-10  0:18 Macy, Kip
2005-06-08 10:42 Ian Pratt
2005-06-09 22:35 ` Daniel Stekloff
2005-06-04 21:51 Ian Pratt
2005-06-05  0:17 ` Kip Macy
2005-06-06 22:28 ` 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=200506040756.26647.dsteklof@us.ibm.com \
    --to=dsteklof@us.ibm.com \
    --cc=kip.macy@gmail.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.