public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: He Kuang <hekuang@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	alexander.shishkin@linux.intel.com, wangnan0@huawei.com,
	jpoimboe@redhat.com, ak@linux.intel.com, eranian@google.com,
	namhyung@kernel.org, adrian.hunter@intel.com,
	sukadev@linux.vnet.ibm.com, masami.hiramatsu.pt@hitachi.com,
	tumanova@linux.vnet.ibm.com, kan.liang@intel.com,
	penberg@kernel.org, dsahern@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 04/14] perf tools: Move unwind__prepare_access from thread_new into thread__insert_map
Date: Wed, 1 Jun 2016 10:39:26 +0200	[thread overview]
Message-ID: <20160601083926.GB13738@krava> (raw)
In-Reply-To: <1464693552-104294-5-git-send-email-hekuang@huawei.com>

On Tue, May 31, 2016 at 11:19:02AM +0000, He Kuang wrote:
> For determine the libunwind methods to use, we should get the
> 32bit/64bit information from maps of a thread. When a thread is newly
> created, the information is not prepared. This patch moves
> unwind__prepare_access() into thread__insert_map() so we can get the
> information we need from maps. Meanwhile, let thread__insert_map()
> return value and show messages on error.
> 
> Signed-off-by: He Kuang <hekuang@huawei.com>
> ---
>  tools/perf/util/machine.c          | 10 ++++++++--
>  tools/perf/util/thread.c           | 13 +++----------
>  tools/perf/util/thread.h           |  2 +-
>  tools/perf/util/unwind-libunwind.c |  7 +++----
>  4 files changed, 15 insertions(+), 17 deletions(-)
> 
> diff --git a/tools/perf/util/machine.c b/tools/perf/util/machine.c
> index bdc33ce..0bd6aac 100644
> --- a/tools/perf/util/machine.c
> +++ b/tools/perf/util/machine.c
> @@ -1353,7 +1353,10 @@ int machine__process_mmap2_event(struct machine *machine,
>  	if (map == NULL)
>  		goto out_problem_map;
>  
> -	thread__insert_map(thread, map);
> +	ret = thread__insert_map(thread, map);
> +	if (ret)
> +		pr_err("Thread insert map error\n");
> +

I think we should fail the function, not just display error

>  	thread__put(thread);
>  	map__put(map);
>  	return 0;
> @@ -1403,7 +1406,10 @@ int machine__process_mmap_event(struct machine *machine, union perf_event *event
>  	if (map == NULL)
>  		goto out_problem_map;
>  
> -	thread__insert_map(thread, map);
> +	ret = thread__insert_map(thread, map);
> +	if (ret)
> +		pr_err("Thread insert map error\n");

same here

jirka

  reply	other threads:[~2016-06-01  8:39 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 11:18 [PATCH v7 00/14] Add support for remote unwind He Kuang
2016-05-31 11:18 ` [PATCH v7 01/14] perf tools: Use LIBUNWIND_DIR for remote libunwind feature check He Kuang
2016-05-31 11:19 ` [PATCH v7 02/14] perf tools: Decouple thread->address_space on libunwind He Kuang
2016-05-31 11:19 ` [PATCH v7 03/14] perf tools: Introducing struct unwind_libunwind_ops for local unwind He Kuang
2016-06-01  8:39   ` Jiri Olsa
2016-06-01  8:39   ` Jiri Olsa
2016-05-31 11:19 ` [PATCH v7 04/14] perf tools: Move unwind__prepare_access from thread_new into thread__insert_map He Kuang
2016-06-01  8:39   ` Jiri Olsa [this message]
2016-05-31 11:19 ` [PATCH v7 05/14] perf tools: Don't mix LIBUNWIND_LIBS into LIBUNWIND_LDFLAGS He Kuang
2016-05-31 11:19 ` [PATCH v7 06/14] perf tools: Separate local/remote libunwind config He Kuang
2016-06-01  8:39   ` Jiri Olsa
2016-05-31 11:19 ` [PATCH v7 07/14] perf tools: Rename unwind-libunwind.c to unwind-libunwind-local.c He Kuang
2016-05-31 11:19 ` [PATCH v7 08/14] perf tools: Extract common API out of unwind-libunwind-local.c He Kuang
2016-05-31 11:19 ` [PATCH v7 09/14] perf tools: Export normalize_arch() function He Kuang
2016-05-31 11:19 ` [PATCH v7 10/14] perf tools: Check the target platform before assigning unwind methods He Kuang
2016-06-01  8:40   ` Jiri Olsa
2016-06-01  8:40   ` Jiri Olsa
2016-06-01 10:02     ` Hekuang
2016-05-31 11:19 ` [PATCH v7 11/14] perf tools: Change fixed name of libunwind__arch_reg_id to macro He Kuang
2016-05-31 11:19 ` [PATCH v7 12/14] perf tools: Introduce flag to separate local/remote unwind compilation He Kuang
2016-05-31 11:19 ` [PATCH v7 13/14] perf callchain: Support x86 target platform He Kuang
2016-06-01  8:40   ` Jiri Olsa
2016-06-01 12:47     ` Arnaldo Carvalho de Melo
2016-06-01 13:14       ` Jiri Olsa
2016-06-01  8:40   ` Jiri Olsa
2016-06-01  9:53     ` Hekuang
2016-06-01  8:41   ` Jiri Olsa
2016-05-31 11:19 ` [PATCH v7 14/14] perf callchain: Support aarch64 cross-platform He Kuang
2016-06-01  8:40   ` Jiri Olsa
2016-06-01  9:54     ` Hekuang

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=20160601083926.GB13738@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=hekuang@huawei.com \
    --cc=jpoimboe@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=penberg@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sukadev@linux.vnet.ibm.com \
    --cc=tumanova@linux.vnet.ibm.com \
    --cc=wangnan0@huawei.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