[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <50531A5D.3010206@gmail.com>
Date: Fri, 14 Sep 2012 05:51:57 -0600
From: David Ahern <dsahern@...il.com>
To: Xiao Guangrong <xiaoguangrong@...ux.vnet.ibm.com>
CC: Dong Hao <haodong@...ux.vnet.ibm.com>, acme@...radead.org,
avi@...hat.com, mtosatti@...hat.com,
Ingo Molnar <mingo@...nel.org>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org
Subject: Re: [PATCH v7 3/3] KVM: perf: kvm events analysis tool
On 9/13/12 8:56 PM, Xiao Guangrong wrote:
> We'd better keep the record/report function, sometimes, we can only get perf.data
> from the customers whose machine can not be reached for us.
>
> Especially, other tracepoints are also interesting for us when the customers encounter
> the performance issue, we always ask costumes to use "perf kvm stat -e xxx" to append
> other events, like lock:*. Then, we can get not only the information of kvm events
> by using 'perf kvm stat' but also other informations like 'perf lock' or 'perf script'
> to get the whole sequences.
Ok.
> And, i think "live mode" is also useful for 'perf lock/sched', could you implement it
> in perf core?
The code will be re-usable, so lock and sched should be able to add a
live mode too.
>
> By the way, the new version of our patchset is ready, do you want to add your implement
> after it is accepted by Arnaldo? Or are you going to post it with our patchset together?
Then go ahead and submit it for inclusion; I'll add my stuff on top.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists