From: Josh Triplett <josh@freedesktop.org>
To: Daniel Stekloff <dsteklof@us.ibm.com>
Cc: Xen Mailing List <xen-devel@lists.xensource.com>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: [PATCH] xenstat - printing out of order enabled vcpu usage
Date: Sat, 22 Oct 2005 12:33:16 -0700 [thread overview]
Message-ID: <435A93FC.2050303@freedesktop.org> (raw)
In-Reply-To: <1129939843.3236.52.camel@w-stekloff.beaverton.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 803 bytes --]
Daniel Stekloff wrote:
> This patch is to make xentop able to print vcpu usage for out of order
> enabled vcpus in a domain. This really isn't an issue anymore with the
> changes made to dom0 ops and xm/xend.
>
> But, I provide it because:
>
> - Josh noticed my previous patch called getvcpuinfo twice for each vpcu,
> which was completely silly.
>
> - this patch would be useful in the remote chance that domain vpcus are
> enabled out of order.
>
>
> Dan
>
> Signed-off-by: Daniel Stekloff <dsteklof@us.ibm.com>
This patch looks good to me.
Signed-off-by: Josh Triplett <josh@freedesktop.org>
I've merged this patch into the new xenstat tree at
<http://xenbits.xensource.com/ext/xen-xenstat.hg>. Christian, could you
please pull the xenstat tree to xen-unstable? Thanks.
- Josh Triplett
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2005-10-22 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-22 0:10 [PATCH] xenstat - printing out of order enabled vcpu usage Daniel Stekloff
2005-10-22 19:33 ` Josh Triplett [this message]
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=435A93FC.2050303@freedesktop.org \
--to=josh@freedesktop.org \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=dsteklof@us.ibm.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.