All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Ben Thomas <bthomas@virtualiron.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] getvcpuinfo additional information
Date: Tue, 7 Nov 2006 22:19:15 +0000	[thread overview]
Message-ID: <20061107221915.GD25965@redhat.com> (raw)
In-Reply-To: <45510125.10606@virtualiron.com>

On Tue, Nov 07, 2006 at 04:56:53PM -0500, Ben Thomas wrote:
> On a number of instances, it has proved quite useful to be able to
> easily examine more of the VCPU state. Specifically, the information
> contained in the runstate structure.  This patch extends the
> returned information to contain the entire runstate structure.
> A simple usage example is a dom0 user-mode program that can dump all
> of the times for each VCPU (eg, running, blocked, runnable).

[snip]

> Index: xen-unstable.hg/xen/include/public/domctl.h
> ===================================================================
> --- xen-unstable.hg.orig/xen/include/public/domctl.h    2006-11-06 17:12:03.000000000 -0500
> +++ xen-unstable.hg/xen/include/public/domctl.h 2006-11-06 17:12:08.000000000 -0500
> @@ -15,6 +15,7 @@
> #endif
>
>  #include "xen.h"
> +#include "vcpu.h"
>
>  #define XEN_DOMCTL_INTERFACE_VERSION 0x00000004
>
> @@ -239,8 +240,8 @@
>      uint8_t  online;                  /* currently online (not hotplugged)? */
>      uint8_t  blocked;                 /* blocked waiting for an event? */
>      uint8_t  running;                 /* currently scheduled on its CPU? */
> -    uint64_t cpu_time;                /* total cpu time consumed (ns) */
>      uint32_t cpu;                     /* current mapping   */
> +    vcpu_runstate_info_t runstate;    /* VCPU runstate info (see vcpu.h) */
>  };
>  typedef struct xen_domctl_getvcpuinfo xen_domctl_getvcpuinfo_t;
>  DEFINE_XEN_GUEST_HANDLE(xen_domctl_getvcpuinfo_t);

While I like the improved information reporting this change gives us, this is
breaking the HV <-> Dom0  management API...yet again. At very least the 
XEN_DOMCTL_INTERFACE_VERSION version should be incremented, but personally
I'd like to see API & ABI stability maintained by leaving the existing
hypercall alone & adding a new hypercall which deals with extra data.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

  reply	other threads:[~2006-11-07 22:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-07 21:56 [PATCH] getvcpuinfo additional information Ben Thomas
2006-11-07 22:19 ` Daniel P. Berrange [this message]
2006-11-07 22:33   ` Ben Thomas
2006-11-08  0:08     ` Daniel P. Berrange

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=20061107221915.GD25965@redhat.com \
    --to=berrange@redhat.com \
    --cc=bthomas@virtualiron.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.