linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	David Ahern <dsahern@gmail.com>,
	Pekka Enberg <penberg@kernel.org>
Subject: Re: [PATCH 2/2] perf trace: Fix segfault on perf trace -i perf.data
Date: Tue, 12 Nov 2013 21:27:23 +0000	[thread overview]
Message-ID: <20131112212723.GA14439@danjae> (raw)
In-Reply-To: <20131112115700.GC4053@ghostprotocols.net>

Hi Arnaldo,

On Tue, Nov 12, 2013 at 08:57:00AM -0300, Arnaldo Carvalho de Melo wrote:
> So this becomes the first part of this patch, split from yours and
> massaged a bit so that by looking at the patch it becomes quickly clear
> what it is doing, please let me now if I can keep this as-is (with your
> authorship, etc).

Looks good to me.

But I just have a nitpick, please see below.

> 
> I'll test this all out after finishing the next part of the split up.
> 
> commit 296f6ce34590099740bfe03ced37f6f53a0133f8
> Author: Namhyung Kim <namhyung@kernel.org>
> Date:   Tue Nov 12 08:51:45 2013 -0300
> 
>     perf trace: Separate tp syscall field caching into init routine to be reused
>     
>     We need to set this in evsels coming out of a perf.data file header, not
>     just for new ones created for live sessions.
> 
>     So separate the code that caches the syscall entry/exit tracepoint
>     format fields into a new function that will be used in the next
>     changeset.
>     
>     Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>     Cc: Adrian Hunter <adrian.hunter@intel.com>
>     Cc: David Ahern <dsahern@gmail.com>
>     Cc: Frederic Weisbecker <fweisbec@gmail.com>
>     Cc: Jiri Olsa <jolsa@redhat.com>
>     Cc: Mike Galbraith <efault@gmx.de>
>     Cc: Paul Mackerras <paulus@samba.org>
>     Cc: Peter Zijlstra <peterz@infradead.org>
>     Cc: Stephane Eranian <eranian@google.com>
>     Link: http://lkml.kernel.org/n/tip-iv4vbx2064hc2drv38egqzee@git.kernel.org
>     Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> 
> diff --git a/tools/perf/builtin-trace.c b/tools/perf/builtin-trace.c
> index aeb6296a76bd..3fa1dce6d43e 100644
> --- a/tools/perf/builtin-trace.c
> +++ b/tools/perf/builtin-trace.c
> @@ -149,20 +149,32 @@ static void perf_evsel__delete_priv(struct perf_evsel *evsel)
>  	perf_evsel__delete(evsel);
>  }
>  
> +static int perf_evsel__init_syscall_tp(struct perf_evsel *evsel, void *handler)
> +{
> +	evsel->priv = malloc(sizeof(struct syscall_tp));
> +	if (evsel->priv != NULL) {
> +		if (perf_evsel__init_sc_tp_uint_field(evsel, id))
> +			goto out_delete;
> +
> +		evsel->handler = handler;
> +		return 0;
> +	}
> +
> +	return -ENOMEM;
> +
> +out_delete:
> +	free(evsel->priv);
> +	evsel->priv = NULL;

Is this part needed?  I can see that perf_evsel__delete_priv() can do
it for you anyway.  Yes I know it's needed for my later change, but I
think we do it a bit differently.

And again, is perf_evsel__delete_priv() needed?  Isn't the ->priv is
not used for anything else?  Why not just letting perf_evsel__delete()
handle this transparently?

Looking at the source, evsel->priv is a member of union and the other
member ->id_offset is used in when dealing with the perf file header
and it doesn't allocate memory.

Hmm, how about adding a new field like ->needs_free_priv then?

Anyway, it should definitely be a different change, I just want to
raise an issue after seeing it.

Thanks,
Namhyung


> +	return -ENOENT;
> +}
> +
>  static struct perf_evsel *perf_evsel__syscall_newtp(const char *direction, void *handler)
>  {
>  	struct perf_evsel *evsel = perf_evsel__newtp("raw_syscalls", direction);
>  
>  	if (evsel) {
> -		evsel->priv = malloc(sizeof(struct syscall_tp));
> -
> -		if (evsel->priv == NULL)
> +		if (perf_evsel__init_syscall_tp(evsel, handler))
>  			goto out_delete;
> -
> -		if (perf_evsel__init_sc_tp_uint_field(evsel, id))
> -			goto out_delete;
> -
> -		evsel->handler = handler;
>  	}
>  
>  	return evsel;

  parent reply	other threads:[~2013-11-12 12:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12  6:24 [PATCH 1/2] perf trace: Beautify fifth argument of mmap() as fd Namhyung Kim
2013-11-12  6:25 ` [PATCH 2/2] perf trace: Fix segfault on perf trace -i perf.data Namhyung Kim
2013-11-12 11:46   ` Arnaldo Carvalho de Melo
2013-11-12 11:57     ` Arnaldo Carvalho de Melo
2013-11-12 12:15       ` Arnaldo Carvalho de Melo
2013-11-12 21:31         ` Namhyung Kim
2013-11-12 21:27       ` Namhyung Kim [this message]
2013-11-12 13:23         ` Arnaldo Carvalho de Melo
2013-11-12 21:56       ` [tip:perf/urgent] perf trace: Separate tp syscall field caching into init routine to be reused tip-bot for Namhyung Kim
2013-11-12 21:56   ` [tip:perf/urgent] perf trace: Fix segfault on perf trace -i perf.data tip-bot for Namhyung Kim
2013-11-12 15:50 ` [PATCH 1/2] perf trace: Beautify fifth argument of mmap() as fd David Ahern
2013-11-12 21:56 ` [tip:perf/urgent] " tip-bot for 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=20131112212723.GA14439@danjae \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.org \
    --cc=penberg@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;
as well as URLs for NNTP newsgroup(s).