All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sandro Sigala <sandro@roxantis.com>
To: xen-devel@lists.xensource.com
Cc: Emilio Bruna <emilio.bruna@heliman.it>
Subject: xmlrpc: floating point cpu_time value always rounded to nearest integer
Date: Sun, 08 Feb 2009 11:16:50 +0100	[thread overview]
Message-ID: <498EB112.3000302@roxantis.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1211 bytes --]

Hello,

I wrote a program that fetches the status of the Xen domains though the Xen
XMLRPC API (port 8006), with

	(xend-tcp-xmlrpc-server yes)

enabled in /etc/xen/xend-config.sxp.

For the domains I'm getting results like:

    ...
    <value>
        <array>
            <data>
                <value>cpu_time</value>
                <value>
                    <double>17,000000</double>
                </value>
            </data>
        </array>
    </value>
    ...

then (after some running time):

    ...
    <value>
        <array>
            <data>
                <value>cpu_time</value>
                <value>
                    <double>18,000000</double>
                </value>
            </data>
        </array>
    </value>
    ...

Do you know any reasons why the values are rounded to the next integer?

The system I'm using is:

(XEN) Xen version 3.2.1-rc1-pre (buildd@buildd) (gcc version 4.2.3 (Ubuntu
4.2.3-2ubuntu7)) Fri Apr 11 01:13:51 UTC 2008

And I'm using the XMLRPC++ library for accessing the data.

Attached is the full log of the XMLRPC output.

Thanks in advance,
Sandro


-- 
www.roxantis.com - sandro@roxantis.com
Phone: (+39) 347 444 3326 - Fax: (+39) 030 553 1263

[-- Attachment #2: rpcdebug.zip --]
[-- Type: application/x-zip-compressed, Size: 17454 bytes --]

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

                 reply	other threads:[~2009-02-08 10:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=498EB112.3000302@roxantis.com \
    --to=sandro@roxantis.com \
    --cc=emilio.bruna@heliman.it \
    --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.