All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Zhigang Wang <zhigang.x.wang@oracle.com>,
	Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	xen-devel@lists.xen.org, ian.jackson@eu.citrix.com,
	stefano.stabellini@eu.citrix.com
Subject: Re: [PATCH] tools: remove unused wrappers for python
Date: Thu, 8 Oct 2015 16:27:01 +0100	[thread overview]
Message-ID: <1444318021.1410.242.camel@citrix.com> (raw)
In-Reply-To: <56168747.6050109@oracle.com>

On Thu, 2015-10-08 at 11:09 -0400, Zhigang Wang wrote:
> On 10/08/2015 10:38 AM, Ian Campbell wrote:
> > On Tue, 2015-10-06 at 11:24 -0400, Zhigang Wang wrote:
> > > We use these extentions along with xend XMLRPC API/xm. Even when move
> > > to
> > > xl, this will give us a choice to reserve some logic.
> > 
> > There are a lot of interfaces here, are you using all of them? If not
> > then
> > could you enumerate the ones you care about please.
> 
> Currently we are using:
> 
>  xc.getcpuinfo()
>  xc.domain_getinfo()

Thanks.

> But after switching to xl, we cannot get info from xend any more, then some of
> these interfaces may be helpful.

Do you have any insight into what info you currently get from xend which
you don't think you can get from xl?

It may be that there are gaps in the xl functionality which should be
filled, rather than keeping the Python xc bindings around (equally there
may be things where those bindings are the best solution).

Ian.

  reply	other threads:[~2015-10-08 15:27 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 10:46 [PATCH] tools: remove unused wrappers for python Juergen Gross
2015-10-06 11:18 ` Wei Liu
2015-10-06 11:33   ` Juergen Gross
2015-10-06 11:39     ` Wei Liu
2015-10-06 13:40       ` Ian Campbell
2015-10-06 14:51         ` Juergen Gross
2015-10-06 15:11           ` Ian Campbell
2015-10-06 15:21             ` Juergen Gross
2015-10-06 15:26               ` Ian Campbell
2015-10-06 15:30                 ` Zhigang Wang
2015-10-06 15:45                   ` Ian Campbell
2015-10-06 16:14                     ` Juergen Gross
2015-10-06 16:24                       ` Ian Campbell
2015-10-08  1:10                         ` Konrad Rzeszutek Wilk
2015-10-08  4:16                           ` Juergen Gross
2015-10-08 14:30                             ` Ian Campbell
2015-10-06 15:38                 ` Andrew Cooper
2015-10-06 16:31                   ` Wei Liu
2015-10-06 16:38                     ` Ian Campbell
2015-10-06 16:42                       ` Wei Liu
2015-10-06 15:24           ` Zhigang Wang
2015-10-08 14:38             ` Ian Campbell
2015-10-08 15:09               ` Zhigang Wang
2015-10-08 15:27                 ` Ian Campbell [this message]
2015-10-08 16:32                   ` Zhigang Wang
2015-10-08 16:58                     ` Wei Liu
2015-10-09  4:42                     ` Juergen Gross
2015-10-09  9:43                       ` Ian Campbell
2015-10-09 10:16                         ` Juergen Gross
2015-10-09 13:29                       ` Andrew Cooper
2015-10-07  2:58   ` Marek Marczykowski-Górecki

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=1444318021.1410.242.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jgross@suse.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zhigang.x.wang@oracle.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.