Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1563933
| From | David Carrillo-Cisneros <davidcc@google.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2 2/2] perf/core: Remove perf_cpu_context::unique_pmu |
| Date | 2017-01-20 22:50 +0100 |
| Message-ID | <t1Pei-48I-23@gated-at.bofh.it> (permalink) |
| References | <t145H-86O-7@gated-at.bofh.it> <t145I-86O-33@gated-at.bofh.it> <t1Gun-7bo-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Jan 20, 2017 at 1:20 AM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Jan 18, 2017 at 11:24:54AM -0800, David Carrillo-Cisneros wrote:
>> cpuctx->unique_pmu was originally introduced as a way to identify cpuctxs
>> with shared pmus in order to avoid visiting the same cpuctx more than once
>> in a for_each_pmu loop.
>>
>> cpuctx->unique_pmu == cpuctx->pmu in non-software task contexts since they
>> have only one pmu per cpuctx. Since perf_pmu_sched_task is only called in
>> hw contexts, this patch replaces cpuctx->unique_pmu by cpuctx->pmu in it.
>>
>> The change above, together with the previous patch in this series, removed
>> the remaining uses of cpuctx->unique_pmu, so we remove it altogether.
>>
>> Signed-off-by: David Carrillo-Cisneros <davidcc@google.com>
>> Acked-by: Mark Rutland <mark.rutland@arm.com>
>
>
>> @@ -8572,37 +8572,10 @@ static struct perf_cpu_context __percpu *find_pmu_context(int ctxn)
>> return NULL;
>> }
>>
>> -static void update_pmu_context(struct pmu *pmu, struct pmu *old_pmu)
>> -{
>> - int cpu;
>> -
>> - for_each_possible_cpu(cpu) {
>> - struct perf_cpu_context *cpuctx;
>> -
>> - cpuctx = per_cpu_ptr(pmu->pmu_cpu_context, cpu);
>> -
>> - if (cpuctx->unique_pmu == old_pmu)
>> - cpuctx->unique_pmu = pmu;
>> - }
>> -}
>> -
>> static void free_pmu_context(struct pmu *pmu)
>> {
>> - struct pmu *i;
>> -
>> mutex_lock(&pmus_lock);
>> - /*
>> - * Like a real lame refcount.
>> - */
>> - list_for_each_entry(i, &pmus, entry) {
>> - if (i->pmu_cpu_context == pmu->pmu_cpu_context) {
>> - update_pmu_context(i, pmu);
>> - goto out;
>> - }
>> - }
>> -
>> free_percpu(pmu->pmu_cpu_context);
>> -out:
>> mutex_unlock(&pmus_lock);
>> }
>
> This very much relies on us never calling perf_pmu_unregister() on the
> software PMUs afaict. A condition not mention in the Changelog.
>
What's a good way to solve this? Update the Changelog or add code to
update ctx->pmu?
This issue would go away cleanly if we were to remove the context
sharing across pmu's. Would you support work in that direction?
Thanks,
David
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v2 0/2] Optimize cgroup ctx switch and remove cpuctx->unique_pmu David Carrillo-Cisneros <davidcc@google.com> - 2017-01-18 20:30 +0100
[PATCH v2 2/2] perf/core: Remove perf_cpu_context::unique_pmu David Carrillo-Cisneros <davidcc@google.com> - 2017-01-18 20:30 +0100
Re: [PATCH v2 2/2] perf/core: Remove perf_cpu_context::unique_pmu Peter Zijlstra <peterz@infradead.org> - 2017-01-20 13:30 +0100
Re: [PATCH v2 2/2] perf/core: Remove perf_cpu_context::unique_pmu Mark Rutland <mark.rutland@arm.com> - 2017-01-20 15:30 +0100
Re: [PATCH v2 2/2] perf/core: Remove perf_cpu_context::unique_pmu David Carrillo-Cisneros <davidcc@google.com> - 2017-01-20 22:50 +0100
[tip:perf/core] perf/core: Remove perf_cpu_context::unique_pmu tip-bot for David Carrillo-Cisneros <tipbot@zytor.com> - 2017-01-30 13:00 +0100
[PATCH v2 1/2] perf/core: Make cgroup switch visit only cpuctxs with cgroup events David Carrillo-Cisneros <davidcc@google.com> - 2017-01-18 20:30 +0100
[tip:perf/core] perf/core: Make cgroup switch visit only cpuctxs with cgroup events tip-bot for David Carrillo-Cisneros <tipbot@zytor.com> - 2017-01-30 13:00 +0100
csiph-web