linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: mingo@kernel.org, peterz@infradead.org,
	linux-kernel@vger.kernel.org, hemant@linux.vnet.ibm.com,
	naveen.n.rao@linux.vnet.ibm.com
Subject: Re: [PATCH v2 2/3] perf kvm: enable record|report feature on powerpc
Date: Tue, 2 Feb 2016 14:36:48 +0530	[thread overview]
Message-ID: <56B071A8.4060402@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160201210605.GE20817@kernel.org>

HI acme,

On Tuesday 02 February 2016 02:36 AM, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jan 22, 2016 at 11:28:11AM +0530, Ravi Bangoria escreveu:
>> +	return event->header.misc & PERF_RECORD_MISC_CPUMODE_MASK;
>> +}
> This hunk and the next should be on the previous patch, that is not even
> compiling...
>
> You have to compile patch by patch, we can't just test at the end of a
> patchkit like this, this destroys bisection ;-\

Didn't aware about that. Will take care of compiling each patch
separately next time onwards.

> Also you first need to put in place a way to override how to obtain the
> cpumode, then you should use it.
>
> Also this mode doesn't look feasible at all, think about processing
> perf.data files generated in !powerpc systems being analysed in a
> powerpc system. This has to be dependend on the architecture of the
> machine where the perf.data file was recorded, not on the archictecture
> of the machine the binary was built for.

Valid point.

I'll re-think about approach in this case.

> It is only when you do live analysis, like with 'perf trace' and 'perf
> top' that its guaranteed to be all on the same machine.
>
> IIRC in one of the patches in this series you introduce and use a
> library function on the same patch, please break it into two patches as
> well, lemme see what is the name...
>
> Yeah, it is also in this patch:
>
> perf_evlist__arch_add_default(struct perf_evlist *evlist)
>
> Please add this in a separate patch, stating in the changeset comment
> why it is needed and how architectures can override it.

Will do that. Thanks for reviewing.

Regards,
Ravi

  reply	other threads:[~2016-02-02  9:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22  5:58 [PATCH v2 0/3] perf kvm: Guest Symbol Resolution for powerpc Ravi Bangoria
2016-01-22  5:58 ` [PATCH v2 1/3] perf kvm: Introduce evsel as argument to perf_event__preprocess_sample Ravi Bangoria
2016-02-01 20:53   ` Arnaldo Carvalho de Melo
2016-02-02  9:07     ` Ravi Bangoria
2016-01-22  5:58 ` [PATCH v2 2/3] perf kvm: enable record|report feature on powerpc Ravi Bangoria
2016-02-01 21:06   ` Arnaldo Carvalho de Melo
2016-02-02  9:06     ` Ravi Bangoria [this message]
2016-02-09 10:47       ` Ravi Bangoria
2016-01-22  5:58 ` [PATCH v2 3/3] perf kvm: Fix output fields instead of 'trace' for perf kvm report " Ravi Bangoria

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=56B071A8.4060402@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;
as well as URLs for NNTP newsgroup(s).