From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: xen-devel@lists.xen.org, Stefan Kuhne <stefan.kuhne@gmx.net>
Subject: Re: Using collectd: CPUFreq in dom0
Date: Mon, 7 Jan 2013 14:13:23 -0500 [thread overview]
Message-ID: <20130107191323.GE8615@phenom.dumpdata.com> (raw)
In-Reply-To: <3263568.20130107172710@eikelenboom.it>
> > Hope this helps.
>
> > It might be just easier to expand the 'xenpm' code to be invoked from
> > your collect scripts?
>
> Would be nice to make xenpm have a better "machine readable" output, the current "human readable" output is a bit hard to parse by scripts.
That could also be done. I have no idea what a machine readable output would be
for this. Is this something you are volunteering to do :-)? We could always use
more patches.
next prev parent reply other threads:[~2013-01-07 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 18:55 Using collectd: CPUFreq in dom0 Stefan Kuhne
2013-01-04 21:11 ` Konrad Rzeszutek Wilk
2013-01-04 21:29 ` Stefan Kuhne
2013-01-07 6:54 ` Jan Beulich
2013-01-07 15:53 ` Konrad Rzeszutek Wilk
2013-01-07 16:27 ` Sander Eikelenboom
2013-01-07 19:13 ` Konrad Rzeszutek Wilk [this message]
2013-01-07 19:20 ` Sander Eikelenboom
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=20130107191323.GE8615@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=linux@eikelenboom.it \
--cc=stefan.kuhne@gmx.net \
--cc=xen-devel@lists.xen.org \
/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.