From: David Ahern <dsahern@gmail.com>
To: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
Cc: acme@ghostprotocols.net, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Runzhen Wang <runzhen@linux.vnet.ibm.com>
Subject: Re: [PATCH 9/9] perf kvm stat report: Add option to analyze specific VM
Date: Mon, 05 Aug 2013 10:57:47 -0400 [thread overview]
Message-ID: <51FFBD6B.8060201@gmail.com> (raw)
In-Reply-To: <51FF4CE2.30703@linux.vnet.ibm.com>
On 8/5/13 2:57 AM, Xiao Guangrong wrote:
> On 08/03/2013 04:05 AM, David Ahern wrote:
>> Add an option to analyze a specific VM within a data file. This
>> allows the collection of kvm events for all VMs and then analyze
>> data for each VM (or set of VMs) individually.
>
> Interesting.
>
> But how can we know which pid is the guest's pid after collecting
> the info. Even if the .data file is moved to another box to do
> off-analyze?
>
Up to the user to be able to leverage the option by collecting what ever
information is needed to correlate a qemu pid with a guest VM.
I have 2 use cases. In one I have a set of shell scripts for managing VMs:
Id Profile PID IP Address Description
-- ---------------- ----- --------------- ----------------
01 ubuntu10 - 172.16.128.51 Ubuntu 10.04 LTS
02 f12-x86_64 8841 172.16.128.52 Fedora 12, x86_64
05 f10-i386 - 172.16.128.55 Fedora 10, i386
07 f16-i386 - 172.16.128.57
08 f16-x86_64 - 172.16.128.58
09 rhel5.5-i386 14716 172.16.128.59 RHEL 5.5, i386
10 f10-x86_64 - 172.16.128.60
12 rhel47-vm1 - 172.16.128.62 rhel4.7 - 32-bit
13 f17 - 172.16.128.63 Fedora 17, x86_64
15 f14 - 172.16.128.65 Fedora 14 - x86_64
16 f10-ppc - 172.16.128.66
17 f12-ppc - 172.16.128.67
19 f16-ppc - 172.16.128.69
20 f16-i386-2 - 172.16.128.70 clone of f16-i386
21 f18-controller 29590 172.16.128.71 cloud controller
22 f18 29541 172.16.128.72 Fedora 18 - x86_64
Collecting that information allows me to correlate kvm data to a VM pid.
I can collect the events for the system and then analyze for a specific VM.
In the second use case (product based) there are 2 VMs and a different
qemu binary name (along with command line arguments) for telling them apart.
David
prev parent reply other threads:[~2013-08-05 14:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-02 20:05 [PATCH 0/9] perf: kvm live mode David Ahern
2013-08-02 20:05 ` [PATCH 1/9] perf top: move CONSOLE_CLEAR to header file David Ahern
2013-08-12 10:19 ` [tip:perf/core] " tip-bot for David Ahern
2013-08-02 20:05 ` [PATCH 2/9] perf stats: add max and min stats David Ahern
2013-08-05 6:02 ` Xiao Guangrong
2013-08-12 10:19 ` [tip:perf/core] perf stats: Add " tip-bot for David Ahern
2013-08-02 20:05 ` [PATCH 3/9] perf session: export a few functions for event processing David Ahern
2013-08-12 10:19 ` [tip:perf/core] perf session: Export " tip-bot for David Ahern
2013-08-02 20:05 ` [PATCH 4/9] perf kvm: split out tracepoints from record args David Ahern
2013-08-05 5:09 ` Xiao Guangrong
2013-08-05 15:41 ` Arnaldo Carvalho de Melo
2013-08-12 10:19 ` [tip:perf/core] perf kvm: Split " tip-bot for David Ahern
2013-08-02 20:05 ` [PATCH 5/9] perf kvm: add live mode - v3 David Ahern
2013-08-05 5:53 ` Xiao Guangrong
2013-08-05 14:43 ` David Ahern
2013-08-02 20:05 ` [PATCH 6/9] perf kvm: add min and max stats to display David Ahern
2013-08-05 6:09 ` Xiao Guangrong
2013-08-05 14:44 ` David Ahern
2013-08-02 20:05 ` [PATCH 7/9] perf kvm: option to print events that exceed a threshold David Ahern
2013-08-05 6:39 ` Xiao Guangrong
2013-08-05 14:49 ` David Ahern
2013-08-02 20:05 ` [PATCH 8/9] perf kvm: debug for missing vmexit/vmentry event David Ahern
2013-08-05 6:53 ` Xiao Guangrong
2013-08-05 15:00 ` David Ahern
2013-08-02 20:05 ` [PATCH 9/9] perf kvm stat report: Add option to analyze specific VM David Ahern
2013-08-05 6:57 ` Xiao Guangrong
2013-08-05 14:57 ` David Ahern [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=51FFBD6B.8060201@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=runzhen@linux.vnet.ibm.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 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.