From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: kan.liang@intel.com
Cc: peterz@infradead.org, mingo@redhat.com,
linux-kernel@vger.kernel.org, jolsa@kernel.org,
namhyung@kernel.org, adrian.hunter@intel.com,
lukasz.odzioba@intel.com, wangnan0@huawei.com,
hekuang@huawei.com, ast@kernel.org, ak@linux.intel.com
Subject: Re: [PATCH RFC V4 1/6] perf tools: lock to protect namespaces and comm list
Date: Mon, 2 Oct 2017 15:05:28 -0300 [thread overview]
Message-ID: <20171002180528.GC2869@kernel.org> (raw)
In-Reply-To: <1506696477-146932-2-git-send-email-kan.liang@intel.com>
Em Fri, Sep 29, 2017 at 07:47:52AM -0700, kan.liang@intel.com escreveu:
> From: Kan Liang <kan.liang@intel.com>
>
> Add two locks to protect namespaces_list and comm_list.
>
> The lock is only needed for multithreaded code, so using mutex wrappers
> provided by perf tool.
>
> Not all the comm_list/namespaces_list accessing are protected, e.g.
> thread__exec_comm. Because the multithread code for perf top event
> synthesizing does not touch them. They don't need a lock.
They don't need a lock _now_, ok I think we can proceed that way, this
cset should serve as a warning to people working in further
multithreading perf.
- Arnaldo
> Signed-off-by: Kan Liang <kan.liang@intel.com>
> ---
> tools/perf/util/thread.c | 53 +++++++++++++++++++++++++++++++++++++++++++-----
> tools/perf/util/thread.h | 3 +++
> 2 files changed, 51 insertions(+), 5 deletions(-)
>
> diff --git a/tools/perf/util/thread.c b/tools/perf/util/thread.c
> index c09bdb5..bf73117 100644
> --- a/tools/perf/util/thread.c
> +++ b/tools/perf/util/thread.c
> @@ -45,6 +45,8 @@ struct thread *thread__new(pid_t pid, pid_t tid)
> thread->cpu = -1;
> INIT_LIST_HEAD(&thread->namespaces_list);
> INIT_LIST_HEAD(&thread->comm_list);
> + init_rwsem(&thread->namespaces_lock);
> + init_rwsem(&thread->comm_lock);
>
> comm_str = malloc(32);
> if (!comm_str)
> @@ -83,18 +85,26 @@ void thread__delete(struct thread *thread)
> map_groups__put(thread->mg);
> thread->mg = NULL;
> }
> + down_write(&thread->namespaces_lock);
> list_for_each_entry_safe(namespaces, tmp_namespaces,
> &thread->namespaces_list, list) {
> list_del(&namespaces->list);
> namespaces__free(namespaces);
> }
> + up_write(&thread->namespaces_lock);
> +
> + down_write(&thread->comm_lock);
> list_for_each_entry_safe(comm, tmp_comm, &thread->comm_list, list) {
> list_del(&comm->list);
> comm__free(comm);
> }
> + up_write(&thread->comm_lock);
> +
> unwind__finish_access(thread);
> nsinfo__zput(thread->nsinfo);
>
> + exit_rwsem(&thread->namespaces_lock);
> + exit_rwsem(&thread->comm_lock);
> free(thread);
> }
>
> @@ -125,8 +135,8 @@ struct namespaces *thread__namespaces(const struct thread *thread)
> return list_first_entry(&thread->namespaces_list, struct namespaces, list);
> }
>
> -int thread__set_namespaces(struct thread *thread, u64 timestamp,
> - struct namespaces_event *event)
> +static int __thread__set_namespaces(struct thread *thread, u64 timestamp,
> + struct namespaces_event *event)
> {
> struct namespaces *new, *curr = thread__namespaces(thread);
>
> @@ -149,6 +159,17 @@ int thread__set_namespaces(struct thread *thread, u64 timestamp,
> return 0;
> }
>
> +int thread__set_namespaces(struct thread *thread, u64 timestamp,
> + struct namespaces_event *event)
> +{
> + int ret;
> +
> + down_write(&thread->namespaces_lock);
> + ret = __thread__set_namespaces(thread, timestamp, event);
> + up_write(&thread->namespaces_lock);
> + return ret;
> +}
> +
> struct comm *thread__comm(const struct thread *thread)
> {
> if (list_empty(&thread->comm_list))
> @@ -170,8 +191,8 @@ struct comm *thread__exec_comm(const struct thread *thread)
> return last;
> }
>
> -int __thread__set_comm(struct thread *thread, const char *str, u64 timestamp,
> - bool exec)
> +static int ____thread__set_comm(struct thread *thread, const char *str,
> + u64 timestamp, bool exec)
> {
> struct comm *new, *curr = thread__comm(thread);
>
> @@ -195,6 +216,17 @@ int __thread__set_comm(struct thread *thread, const char *str, u64 timestamp,
> return 0;
> }
>
> +int __thread__set_comm(struct thread *thread, const char *str, u64 timestamp,
> + bool exec)
> +{
> + int ret;
> +
> + down_write(&thread->comm_lock);
> + ret = ____thread__set_comm(thread, str, timestamp, exec);
> + up_write(&thread->comm_lock);
> + return ret;
> +}
> +
> int thread__set_comm_from_proc(struct thread *thread)
> {
> char path[64];
> @@ -212,7 +244,7 @@ int thread__set_comm_from_proc(struct thread *thread)
> return err;
> }
>
> -const char *thread__comm_str(const struct thread *thread)
> +static const char *__thread__comm_str(const struct thread *thread)
> {
> const struct comm *comm = thread__comm(thread);
>
> @@ -222,6 +254,17 @@ const char *thread__comm_str(const struct thread *thread)
> return comm__str(comm);
> }
>
> +const char *thread__comm_str(const struct thread *thread)
> +{
> + const char *str;
> +
> + down_read((struct rw_semaphore *)&thread->comm_lock);
> + str = __thread__comm_str(thread);
> + up_read((struct rw_semaphore *)&thread->comm_lock);
> +
> + return str;
> +}
> +
> /* CHECKME: it should probably better return the max comm len from its comm list */
> int thread__comm_len(struct thread *thread)
> {
> diff --git a/tools/perf/util/thread.h b/tools/perf/util/thread.h
> index cb1a5dd..10555d6 100644
> --- a/tools/perf/util/thread.h
> +++ b/tools/perf/util/thread.h
> @@ -9,6 +9,7 @@
> #include "symbol.h"
> #include <strlist.h>
> #include <intlist.h>
> +#include "rwsem.h"
>
> struct thread_stack;
> struct unwind_libunwind_ops;
> @@ -29,7 +30,9 @@ struct thread {
> int comm_len;
> bool dead; /* if set thread has exited */
> struct list_head namespaces_list;
> + struct rw_semaphore namespaces_lock;
> struct list_head comm_list;
> + struct rw_semaphore comm_lock;
> u64 db_id;
>
> void *priv;
> --
> 2.5.5
next prev parent reply other threads:[~2017-10-02 18:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 14:47 [PATCH RFC V4 0/6] perf top optimization kan.liang
2017-09-29 14:47 ` [PATCH RFC V4 1/6] perf tools: lock to protect namespaces and comm list kan.liang
2017-10-02 18:05 ` Arnaldo Carvalho de Melo [this message]
2017-10-02 19:14 ` Liang, Kan
2017-10-02 19:34 ` Arnaldo Carvalho de Melo
2017-10-03 16:44 ` [tip:perf/core] perf tools: Lock " tip-bot for Kan Liang
2017-09-29 14:47 ` [PATCH RFC V4 2/6] perf tools: lock to protect comm_str rb tree kan.liang
2017-10-03 16:45 ` [tip:perf/core] perf tools: Lock " tip-bot for Kan Liang
2017-09-29 14:47 ` [PATCH RFC V4 3/6] perf top: implement multithreading for perf_event__synthesize_threads kan.liang
2017-10-03 16:45 ` [tip:perf/core] perf top: Implement " tip-bot for Kan Liang
2017-09-29 14:47 ` [PATCH RFC V4 4/6] perf top: add option to set the number of thread for event synthesize kan.liang
2017-10-03 16:45 ` [tip:perf/core] perf top: Add " tip-bot for Kan Liang
2017-09-29 14:47 ` [PATCH RFC V4 5/6] perf top: switch to backward overwrite mode kan.liang
2017-09-30 19:48 ` Jiri Olsa
2017-10-02 17:19 ` Liang, Kan
2017-10-02 18:03 ` acme
2017-10-03 8:24 ` Jiri Olsa
2017-09-29 14:47 ` [PATCH RFC V4 6/6] perf top: check the cost of perf_top__mmap_read kan.liang
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=20171002180528.GC2869@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=ast@kernel.org \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.odzioba@intel.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).