public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Stephane Eranian <eranian@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>
Subject: Re: [PATCH 1/4] perf evsel: Add evsel__clone() function
Date: Fri, 18 Sep 2020 15:31:45 +0200	[thread overview]
Message-ID: <20200918133145.GA2626435@krava> (raw)
In-Reply-To: <20200916063129.1061487-2-namhyung@kernel.org>

On Wed, Sep 16, 2020 at 03:31:26PM +0900, Namhyung Kim wrote:

SNIP

> +struct evsel *evsel__clone(struct evsel *orig)
> +{
> +	struct evsel *evsel;
> +	struct evsel_config_term *pos, *tmp;
> +
> +	BUG_ON(orig->core.fd);
> +	BUG_ON(orig->counts);
> +	BUG_ON(orig->priv);
> +	BUG_ON(orig->per_pkg_mask);
> +
> +	/* cannot handle BPF objects for now */
> +	if (orig->bpf_obj)
> +		return NULL;
> +
> +	evsel = evsel__new(&orig->core.attr);
> +	if (evsel == NULL)
> +		return NULL;
> +
> +	evsel->core.cpus = perf_cpu_map__get(orig->core.cpus);
> +	evsel->core.own_cpus = perf_cpu_map__get(orig->core.own_cpus);
> +	evsel->core.threads = perf_thread_map__get(orig->core.threads);
> +	evsel->core.nr_members = orig->core.nr_members;
> +	evsel->core.system_wide = orig->core.system_wide;
> +
> +	if (orig->name)
> +		evsel->name = strdup(orig->name);
> +	if (orig->group_name)
> +		evsel->group_name = strdup(orig->group_name);
> +	if (orig->pmu_name)
> +		evsel->pmu_name = strdup(orig->pmu_name);
> +	if (orig->filter)
> +		evsel->filter = strdup(orig->filter);

we should check those strdup results

> +	evsel->cgrp = cgroup__get(orig->cgrp);
> +	evsel->tp_format = orig->tp_format;
> +	evsel->handler = orig->handler;
> +	evsel->leader = orig->leader;
> +
> +	evsel->max_events = orig->max_events;
> +	evsel->tool_event = orig->tool_event;
> +	evsel->unit = orig->unit;
> +	evsel->scale = orig->scale;
> +	evsel->snapshot = orig->snapshot;
> +	evsel->per_pkg = orig->per_pkg;
> +	evsel->percore = orig->percore;
> +	evsel->precise_max = orig->precise_max;
> +	evsel->use_uncore_alias = orig->use_uncore_alias;
> +	evsel->is_libpfm_event = orig->is_libpfm_event;
> +
> +	evsel->exclude_GH = orig->exclude_GH;
> +	evsel->sample_read = orig->sample_read;
> +	evsel->auto_merge_stats = orig->auto_merge_stats;
> +	evsel->collect_stat = orig->collect_stat;
> +	evsel->weak_group = orig->weak_group;

so all those evsel's members are possibly defined in parse time right?
perhaps we should separate them in the struct? and make some note about
evsel__clone function that new members should be considered for copy
in evsel__close.. or something like that

> +
> +	list_for_each_entry(pos, &orig->config_terms, list) {
> +		tmp = malloc(sizeof(*tmp));
> +		if (tmp == NULL) {
> +			evsel__delete(evsel);
> +			evsel = NULL;
> +			break;
> +		}
> +
> +		*tmp = *pos;
> +		if (tmp->free_str) {
> +			tmp->val.str = strdup(pos->val.str);
> +			if (tmp->val.str == NULL) {
> +				evsel__delete(evsel);
> +				evsel = NULL;
> +				free(tmp);
> +				break;
> +			}
> +		}
> +		list_add_tail(&tmp->list, &evsel->config_terms);
> +	}

could this go in separate function? copy_terms

thanks,
jirka

> +
> +	return evsel;
> +}
> +
>  /*
>   * Returns pointer with encoded error via <linux/err.h> interface.
>   */
> diff --git a/tools/perf/util/evsel.h b/tools/perf/util/evsel.h
> index 35e3f6d66085..507c31d6a389 100644
> --- a/tools/perf/util/evsel.h
> +++ b/tools/perf/util/evsel.h
> @@ -169,6 +169,7 @@ static inline struct evsel *evsel__new(struct perf_event_attr *attr)
>  	return evsel__new_idx(attr, 0);
>  }
>  
> +struct evsel *evsel__clone(struct evsel *orig);
>  struct evsel *evsel__newtp_idx(const char *sys, const char *name, int idx);
>  
>  /*
> -- 
> 2.28.0.618.gf4bc123cb7-goog
> 


  reply	other threads:[~2020-09-18 13:31 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-16  6:31 [PATCHSET v2 0/4] perf stat: Expand events for each cgroup Namhyung Kim
2020-09-16  6:31 ` [PATCH 1/4] perf evsel: Add evsel__clone() function Namhyung Kim
2020-09-18 13:31   ` Jiri Olsa [this message]
2020-09-21  5:44     ` Namhyung Kim
2020-09-16  6:31 ` [PATCH 2/4] perf stat: Add --for-each-cgroup option Namhyung Kim
2020-09-16 13:51   ` Arnaldo Carvalho de Melo
2020-09-17  1:33     ` Namhyung Kim
2020-09-18 13:34   ` Jiri Olsa
2020-09-21  5:45     ` Namhyung Kim
2020-09-16  6:31 ` [PATCH 3/4] perf tools: Copy metric events properly when expand cgroups Namhyung Kim
2020-09-18 13:45   ` Jiri Olsa
2020-09-21  5:48     ` Namhyung Kim
2020-09-16  6:31 ` [PATCH 4/4] perf test: Add expand cgroup event test Namhyung Kim
2020-09-18 13:51   ` Jiri Olsa
2020-09-21  5:49     ` Namhyung Kim
  -- strict thread matches above, loose matches on Subject: below --
2020-09-08  4:42 [PATCHSET 0/4] perf stat: Add --multiply-cgroup option Namhyung Kim
2020-09-08  4:42 ` [PATCH 1/4] perf evsel: Add evsel__clone() function Namhyung Kim
2020-09-10  8:59   ` Jiri Olsa
2020-09-10 13:18     ` Namhyung Kim

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=20200918133145.GA2626435@krava \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.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