linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: kajoljain <kjain@linux.ibm.com>
Cc: "Jin, Yao" <yao.jin@linux.intel.com>,
	acme@kernel.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>, Jiri Olsa <jolsa@kernel.org>,
	Kan Liang <kan.liang@linux.intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
	Anju T Sudhakar <anju@linux.vnet.ibm.com>,
	Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Subject: Re: [PATCH] tools/perf/metricgroup: Fix printing event names of metric group with multiple events incase of overlapping events
Date: Mon, 20 Jan 2020 10:23:52 +0100	[thread overview]
Message-ID: <20200120092352.GA608405@krava> (raw)
In-Reply-To: <dde66abd-6025-31e3-9bda-a6eb1986eea8@linux.ibm.com>

On Mon, Jan 20, 2020 at 02:23:19PM +0530, kajoljain wrote:
> 
> On 1/8/20 9:32 PM, Jiri Olsa wrote:
> > On Wed, Jan 08, 2020 at 02:41:35PM +0530, kajoljain wrote:
> > 
> > SNIP
> > 
> > > > > -    int i = 0;
> > > > > +    int i = 0, j = 0;
> > > > >        bool leader_found;
> > > > >          evlist__for_each_entry (perf_evlist, ev) {
> > > > > +        j++;
> > > > > +        if (j <= iterator_perf_evlist)
> > > > > +            continue;
> > > > >            if (!strcmp(ev->name, ids[i])) {
> > > > >                if (!metric_events[i])
> > > > >                    metric_events[i] = ev;
> > > > > @@ -146,6 +151,7 @@ static struct evsel *find_evsel_group(struct
> > > > > evlist *perf_evlist,
> > > > >                }
> > > > >            }
> > > > >        }
> > > > > +    iterator_perf_evlist = j;
> > > > >          return metric_events[0];
> > > > >    }
> > > > > 
> > > > Thanks for reporting and fixing this issue.
> > > > 
> > > > I just have one question, do we really need a *static variable* to track
> > > > the matched events? Perhaps using an input parameter?
> > > Hi Jin,
> > > 
> > > The other way I come up with to solve this issue is, making change in
> > > perf_evlist itself by adding some flag in event name, to keep track of
> > > matched events.
> > > 
> > > As if we change event name itself, next time when we compare it won't
> > > matched. But in that case we need to remove those flag later. Which will
> > > increase the
> > > 
> > > complexity. If you have any suggestions, please let me know.
> > we already keep evsel::cpu_iter for similar concept
> > 
> > so I guess we could have some iterator_perf_evlist variable in evlist..
> > that is if we don't find other solution (other than static varable)
> 
> Hi Jiri,
> 
>          Thanks for reviewing the patch. I checked 'evsel::cpu_iter'
> variable, I think it added recently and I am not able to find any similar
> kind of variable in
> 
>          evlist. Please let me know if my understanding is fine. Do you want
> me to add new variable in evlist itself or there is any other way possible.

please check Arnaldo's tree:
  git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git perf/core

jirka

  reply	other threads:[~2020-01-20  9:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-08  6:58 [PATCH] tools/perf/metricgroup: Fix printing event names of metric group with multiple events incase of overlapping events Kajol Jain
2020-01-08  7:25 ` Jin, Yao
2020-01-08  9:11   ` kajoljain
2020-01-08 16:02     ` Jiri Olsa
2020-01-20  8:53       ` kajoljain
2020-01-20  9:23         ` Jiri Olsa [this message]
2020-01-20  9:25           ` Jiri Olsa

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=20200120092352.GA608405@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=anju@linux.vnet.ibm.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=kjain@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=maddy@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.ibm.com \
    --cc=yao.jin@linux.intel.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).