From: David Ahern <dsahern@gmail.com>
To: Alexander Yarygin <yarygin@linux.vnet.ibm.com>,
Hemant Kumar <hemant@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
acme@kernel.org, scottwood@freescale.com,
sukadev@linux.vnet.ibm.com, naveen.n.rao@linux.vnet.ibm.com,
mpe@ellerman.id.au, paulus@samba.org, mingo@redhat.com,
Christian Borntraeger <borntraeger@de.ibm.com>,
linux-s390 <linux-s390@vger.kernel.org>
Subject: Re: [PATCH v8 1/4] perf,kvm/{x86,s390}: Remove dependency on uapi/kvm_perf.h
Date: Mon, 28 Sep 2015 08:31:57 -0600 [thread overview]
Message-ID: <56094F5D.9090805@gmail.com> (raw)
In-Reply-To: <87bncm7l6z.fsf@linux.vnet.ibm.com>
On 9/28/15 7:00 AM, Alexander Yarygin wrote:
>> diff --git a/tools/perf/builtin-kvm.c b/tools/perf/builtin-kvm.c
>> index fc1cffb..ef25fcf 100644
>> --- a/tools/perf/builtin-kvm.c
>> +++ b/tools/perf/builtin-kvm.c
>> @@ -31,20 +31,18 @@
>> #include <math.h>
>>
>> #ifdef HAVE_KVM_STAT_SUPPORT
>> -#include <asm/kvm_perf.h>
>> #include "util/kvm-stat.h"
>>
>> -void exit_event_get_key(struct perf_evsel *evsel,
>> - struct perf_sample *sample,
>> +void exit_event_get_key(struct perf_evsel *evsel, struct perf_sample *sample,
>> struct event_key *key)
>> {
>> key->info = 0;
>> - key->key = perf_evsel__intval(evsel, sample, KVM_EXIT_REASON);
>> + key->key = perf_evsel__intval(evsel, sample, exit_reason_code);
>> }
>>
>> bool kvm_exit_event(struct perf_evsel *evsel)
>> {
>> - return !strcmp(evsel->name, KVM_EXIT_TRACE);
>> + return !strncmp(evsel->name, kvm_events_tp[1], strlen(evsel->name));
>> }
>
> Hmm, direct access to kvm_events_tp? Maybe add a getter for this or
> something like extern char *kvm_exit_trace;?
> /* why strncmp? */
>
>>
>> bool exit_event_begin(struct perf_evsel *evsel,
>> @@ -60,7 +58,7 @@ bool exit_event_begin(struct perf_evsel *evsel,
>>
>> bool kvm_entry_event(struct perf_evsel *evsel)
>> {
>> - return !strcmp(evsel->name, KVM_ENTRY_TRACE);
>> + return !strncmp(evsel->name, kvm_events_tp[0], strlen(evsel->name));
>> }
>>
>> bool exit_event_end(struct perf_evsel *evsel,
I agree; don't rely on kvm_events_tp. Define KVM_ENTRY_TRACE and
KVM_EXIT_TRACE like x86.
next prev parent reply other threads:[~2015-09-28 14:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 6:17 [PATCH v8 1/4] perf, kvm/{x86, s390}: Remove dependency on uapi/kvm_perf.h Hemant Kumar
2015-09-25 6:17 ` [PATCH v8 2/4] perf,kvm/{x86,s390}: Remove const from kvm_events_tp Hemant Kumar
2015-09-25 6:17 ` [PATCH v8 3/4] perf,kvm/powerpc: Port perf kvm stat to powerpc Hemant Kumar
2015-09-25 6:17 ` [PATCH v8 4/4] perf,kvm/powerpc: Add support for HCALL reasons Hemant Kumar
2015-09-28 13:00 ` [PATCH v8 1/4] perf, kvm/{x86, s390}: Remove dependency on uapi/kvm_perf.h Alexander Yarygin
2015-09-28 14:31 ` David Ahern [this message]
2015-09-28 15:16 ` [PATCH v8 1/4] perf,kvm/{x86,s390}: " Scott Wood
2015-09-28 15:21 ` David Ahern
2015-09-30 18:14 ` [PATCH v8 1/4] perf, kvm/{x86, s390}: " Hemant Kumar
2015-09-30 18:12 ` Hemant Kumar
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=56094F5D.9090805@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@kernel.org \
--cc=borntraeger@de.ibm.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=naveen.n.rao@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=yarygin@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).