From: David Ahern <dsahern@gmail.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>,
Arnaldo Carvalho de Melo <acme@infradead.org>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
KVM <kvm@vger.kernel.org>
Subject: Re: [PATCH 3/3] KVM: perf: kvm events analysis tool
Date: Wed, 15 Feb 2012 22:05:08 -0700 [thread overview]
Message-ID: <4F3C8E84.80905@gmail.com> (raw)
In-Reply-To: <4F3C8D3F.9010105@linux.vnet.ibm.com>
On 2/15/12 9:59 PM, Xiao Guangrong wrote:
>
>
> Okay, i will post the next version after collecting your new comments!
>
> Thanks for your time, David! :)
>
I had more comments, but got sidetracked and forgot to come back to
this. I still haven't looked at the code yet, but some comments from
testing:
1. The error message:
Warning: Error: expected type 5 but read 4
Warning: Error: expected type 5 but read 0
Warning: unknown op '}'
is fixed by this patch which has not yet made its way into perf:
https://lkml.org/lkml/2011/9/4/41
The most recent request:
https://lkml.org/lkml/2012/2/8/479
Arnaldo: the patch still applies cleanly (but with an offset of -2 lines).
2. negatve testing:
perf kvm-events record -e kvm:* -p 2603 -- sleep 10
Warning: Error: expected type 4 but read 7
Warning: Error: expected type 5 but read 0
Warning: failed to read event print fmt for kvm_apic
Warning: Error: expected type 4 but read 7
Warning: Error: expected type 5 but read 0
Warning: failed to read event print fmt for kvm_inj_exception
Fatal: bad op token {
If other kvm events are specified in the record line they appear to be
silently ignored in the report in which case why allow the -e option to
record?
3. What is happening for multiple VMs?
a. perf kvm-events report
data is collected for all VMs. What is displayed in the report? An
average for all VMs?
b. perf kvm-events report --vcpu 1
Does this given an average of all vcpu 1's?
Perhaps a -p option for the report to pull out events related to a
single VM. Really this could be a generic option (to perf-report and
perf-script as well) to only show/analyze events for the specified pid.
ie., data is recorded for all VMs (or system wide for the regular
perf-record) and you want to only consider events for a specific pid.
e.g., in process_sample_event() skip event if event->ip.pid !=
report_pid (works for perf code because PERF_SAMPLE_TID attribute is
always set).
David
next prev parent reply other threads:[~2012-02-16 5:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-13 5:32 [PATCH 3/3] KVM: perf: kvm events analysis tool David Ahern
2012-02-13 10:06 ` Xiao Guangrong
2012-02-13 15:52 ` David Ahern
2012-02-16 4:59 ` Xiao Guangrong
2012-02-16 5:05 ` David Ahern [this message]
2012-02-16 5:33 ` Xiao Guangrong
2012-02-16 16:35 ` Arnaldo Carvalho de Melo
-- strict thread matches above, loose matches on Subject: below --
2012-03-06 8:55 [PATCH v5 0/3] " Xiao Guangrong
2012-03-06 8:58 ` [PATCH 3/3] " Xiao Guangrong
2012-02-09 9:06 [PATCH v4 0/3] " Xiao Guangrong
2012-02-09 9:09 ` [PATCH 3/3] " Xiao Guangrong
2012-02-13 3:04 ` David Ahern
2012-02-13 5:00 ` Xiao Guangrong
2012-02-20 23:47 ` David Ahern
2012-02-21 3:52 ` Xiao Guangrong
2012-02-21 4:58 ` David Ahern
2012-02-27 4:57 ` Xiao Guangrong
2012-01-16 9:30 [RFC][PATCH] KVM: perf: a smart tool to analyse kvm events Xiao Guangrong
2012-01-16 9:32 ` [PATCH 3/3] KVM: perf: kvm events analysis tool Xiao Guangrong
2012-01-16 10:04 ` Avi Kivity
2012-01-17 2:30 ` Xiao Guangrong
2012-01-24 12:49 ` Avi Kivity
2012-01-16 10:08 ` Stefan Hajnoczi
2012-01-17 2:37 ` Xiao Guangrong
2012-01-17 11:59 ` Marcelo Tosatti
2012-01-24 12:51 ` 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=4F3C8E84.80905@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@infradead.org \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=xiaoguangrong@linux.vnet.ibm.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).