From: Peter Zijlstra <peterz@infradead.org>
To: kan.liang@linux.intel.com
Cc: mingo@redhat.com, acme@kernel.org, tglx@linutronix.de,
bp@alien8.de, linux-kernel@vger.kernel.org, eranian@google.com,
alexey.budankov@linux.intel.com, vitaly.slobodskoy@intel.com,
ak@linux.intel.com
Subject: Re: [RFC PATCH V2 2/7] perf: Init/fini PMU specific data
Date: Mon, 6 Jan 2020 11:38:32 +0100 [thread overview]
Message-ID: <20200106103832.GO2810@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1578080364-5928-2-git-send-email-kan.liang@linux.intel.com>
On Fri, Jan 03, 2020 at 11:39:19AM -0800, kan.liang@linux.intel.com wrote:
> From: Kan Liang <kan.liang@linux.intel.com>
>
> The PMU specific data for the monitored tasks only be allocated during
> LBR call stack monitoring.
>
> When a LBR call stack event is accounted, the perf_ctx_data for related
> tasks will be allocated/initialized by init_perf_ctx_data().
> When a LBR call stack event is unaccounted, the perf_ctx_data for
> related tasks will be detached/freed by fini_task_ctx_data().
I hate that 'fini' name. We don't use that anywhere else.
> + raw_spin_lock_irqsave(&task_data_sys_wide_events_lock, flags);
> +
> + /*
> + * Allocate perf_ctx_data for all existing threads with the first
> + * system-wide event.
> + * The perf_ctx_data for new threads will be allocated in
> + * perf_event_fork().
> + */
> + if (atomic_inc_return(&nr_task_data_sys_wide_events) > 1)
> + goto unlock;
> +
> + rcu_read_lock();
> + for_each_process_thread(g, p) {
> + mutex_lock(&p->perf_event_mutex);
> + if (p->perf_ctx_data) {
> + /*
> + * The perf_ctx_data for this thread may has been
> + * allocated by per-task event.
> + * Only update refcount for the case.
> + */
> + refcount_inc(&p->perf_ctx_data->refcount);
> + mutex_unlock(&p->perf_event_mutex);
> + continue;
> + }
> +
> + if (pos < num_thread) {
> + refcount_set(&data[pos]->refcount, 1);
> + rcu_assign_pointer(p->perf_ctx_data, data[pos++]);
> + } else {
> + /*
> + * There may be some new threads created,
> + * when we allocate space.
> + * Track the number in nr_new_tasks.
> + */
> + nr_new_tasks++;
> + }
> + mutex_unlock(&p->perf_event_mutex);
> + }
> + rcu_read_unlock();
> +
> + raw_spin_unlock_irqrestore(&task_data_sys_wide_events_lock, flags);
Still NAK. That's some mightly broken code there.
next prev parent reply other threads:[~2020-01-06 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 19:39 [RFC PATCH V2 1/7] perf: Save PMU specific data in task_struct kan.liang
2020-01-03 19:39 ` [RFC PATCH V2 2/7] perf: Init/fini PMU specific data kan.liang
2020-01-06 10:38 ` Peter Zijlstra [this message]
2020-01-06 14:23 ` Andi Kleen
2020-01-06 14:31 ` Peter Zijlstra
2020-01-06 16:18 ` Liang, Kan
2020-01-03 19:39 ` [RFC PATCH V2 3/7] perf: Supply task information to sched_task() kan.liang
2020-01-03 19:39 ` [RFC PATCH V2 4/7] perf/x86/lbr: Fix shorter LBRs call stacks for system-wide mode kan.liang
2020-01-03 19:39 ` [RFC PATCH V2 5/7] perf/x86: Remove swap_task_ctx() kan.liang
2020-01-03 19:39 ` [RFC PATCH V2 6/7] perf: Clean up pmu specific data kan.liang
2020-01-03 19:39 ` [RFC PATCH V2 7/7] perf: Clean up event context from sched_task() 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=20200106103832.GO2810@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexey.budankov@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=vitaly.slobodskoy@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
Powered by JetHome