All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ryota Ozaki <ozaki.ryota@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] expose per-vm statistics via debugfs
Date: Thu, 20 Aug 2009 15:09:48 +0300	[thread overview]
Message-ID: <4A8D3D0C.4060001@redhat.com> (raw)
In-Reply-To: <5e93dcec0908190553k5b7e55aak9987e94b5bdb1893@mail.gmail.com>

On 08/19/2009 03:53 PM, Ryota Ozaki wrote:
> Hi,
>
> This patch let kvm exposes per-vm statistics about
> such as the total number of vm exits, via debugfs.
>
> Existing kvm already collects the per-vm statistics,
> but it has no interface to expose them to users.
> This patch creates directories named a pid of the
> corresponding vm in debugfs of kvm, containing the
> same files that original debugfs exposes.
>
> The per-vm statistics are useful to know activities
> of vms (and to identify anomalous vms for example)
> with more detailed information than cpu and memory
> usage, and network traffics. And also the patch
> introduces no performance overhead, thus, it should
> be familiar with online operations, e.g., dynamic
> adaptation of assigning vm resources using the
> statistics.
>
> Note that this patch requires a trivial modification
> to kvm_stat script. Once this patch is accepted I will
> send a patch for it.
>
> Thanks,
>    ozaki-r
>
>    

My plan is to completely remove the current statistics in favour of 
tracepoints.  You can already display tracepoint statistics with 'perf 
stat' (see tools/perf); tracepoints have the advantage that they can be 
completely disabled at runtime and thus have no performance impact.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-08-20 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19 12:53 [PATCH] expose per-vm statistics via debugfs Ryota Ozaki
2009-08-20 12:09 ` Avi Kivity [this message]
2009-08-20 12:42   ` Ryota Ozaki
2009-08-20 12:49     ` Avi Kivity

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=4A8D3D0C.4060001@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=ozaki.ryota@gmail.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.