From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Avi Kivity <avi@redhat.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Marcelo Tosatti <mtosatti@redhat.com>,
David Ahern <dsahern@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH v5 0/3] KVM: perf: kvm events analysis tool
Date: Tue, 06 Mar 2012 18:42:21 +0800 [thread overview]
Message-ID: <4F55EA0D.4040408@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120306090730.GB27238@elte.hu>
Thanks for your review, Ingo!
On 03/06/2012 05:07 PM, Ingo Molnar wrote:
> So, your new tool has a similar workflow to:
>
> perf kvm record
> perf kvm report
>
> but differs from it in terms of events used and in terms of
> reported output.
>
> To me it appears that your tool is basically pretty similar to
> 'perf stat', adapted to KVM, right?
>
> So, could your new tool's workflow be simplified like this:
>
> perf kvm stat ..
>
> ?
>
> To automatically stat all vcpus in the system, the well-known
> -a/--all-cpus system-wide method could be used:
>
> perf kvm stat -a ...
>
> with stat output following immediately after it has finished.
>
Actually, the stat information has already been included in the report.
> It should also be possible to use those new events in a
> recording fashion - a new, rather logical command sub-space
> could be used for that:
>
> perf kvm stat record ...
> perf kvm stat report ...
>
> [ This could be expanded to regular 'perf stat' as well: 'perf
> stat record' and 'perf stat report' would be useful - but I
> suspect that's outside the scope of your patches. ]
>
I totally agree with you except i prefer 'perf kvm events' to
'perf kvm stat' :) : it records some specified kvm events and
smartly analyze it. I think it matches its doing better.
next prev parent reply other threads:[~2012-03-06 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 8:55 [PATCH v5 0/3] KVM: perf: kvm events analysis tool Xiao Guangrong
2012-03-06 8:56 ` [PATCH 1/3] KVM: x86: export svm/vmx exit code and vector code to userspace Xiao Guangrong
2012-03-06 8:57 ` [PATCH 2/3] KVM: x86: trace mmio begin and complete Xiao Guangrong
2012-03-06 8:58 ` [PATCH 3/3] KVM: perf: kvm events analysis tool Xiao Guangrong
2012-03-06 9:07 ` [PATCH v5 0/3] " Ingo Molnar
2012-03-06 10:42 ` Xiao Guangrong [this message]
2012-03-06 17:12 ` Ingo Molnar
2012-03-07 7:56 ` Xiao Guangrong
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=4F55EA0D.4040408@linux.vnet.ibm.com \
--to=xiaoguangrong@linux.vnet.ibm.com \
--cc=acme@infradead.org \
--cc=avi@redhat.com \
--cc=dsahern@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).