From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-kernel@vger.kernel.org, hemant@linux.vnet.ibm.com,
naveen.n.rao@linux.vnet.ibm.com, Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] perf/kvm: Guest Symbol Resolution for powerpc
Date: Fri, 22 Jan 2016 11:35:51 +0530 [thread overview]
Message-ID: <56A1C6BF.2010602@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160113165936.GP18367@kernel.org>
Hi Arnaldo,
On Wednesday 13 January 2016 10:29 PM, Arnaldo Carvalho de Melo wrote:
> Em Tue, Dec 29, 2015 at 03:38:40PM +0530, Ravi Bangoria escreveu:
>> 'perf kvm {record|report}' is used to record and report the profiled
>> performance of any workload on a guest. From the host, we can collect
>> guest kernel statistics which is useful in finding out any contentions
>> in guest kernel symbols for a certain workload.
>> This feature is not available on powerpc because 'perf' relies on the
>> 'cycles' event (a PMU event) to profile the guest. However, for powerpc,
>> this can't be used from the host because the PMUs are controlled by the
>> guest rather than the host.
> Without entering the realms if the approach is the right one, which I
> leave to PowerPC experts, Ingo, PeterZ, etc:
>
> So, in these cases, please break this into a series, where you, for
> instance, will add that extra evsel parameter to the functions that will
> ultimately use it to extract those event fields, that should be a
> separate patch, so that when reviewing the "meat" of your patch we can
> quickly see what it does, not having to extract that from leg work.
>
> Two other patches should introduce arch__get_{ip,cpumode}().
>
> - Arnaldo
Thanks for suggestion. I've sent v2 with changes you suggested.
Can you please take a look.
Regards,
Ravi
prev parent reply other threads:[~2016-01-22 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 10:08 [PATCH] perf/kvm: Guest Symbol Resolution for powerpc Ravi Bangoria
2016-01-13 16:59 ` Arnaldo Carvalho de Melo
2016-01-22 6:05 ` Ravi Bangoria [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=56A1C6BF.2010602@linux.vnet.ibm.com \
--to=ravi.bangoria@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=hemant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
/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