From: Jiri Olsa <jolsa@redhat.com>
To: Raghavendra Rao Ananta <rananta@codeaurora.org>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
linux-kernel@vger.kernel.org, psodagud@codeaurora.org,
tsoni@codeaurora.org
Subject: Re: [PATCH] perf: Add support for creating offline events
Date: Mon, 12 Feb 2018 10:44:06 +0100 [thread overview]
Message-ID: <20180212094406.GE5821@krava> (raw)
In-Reply-To: <1518217620-28458-1-git-send-email-rananta@codeaurora.org>
On Fri, Feb 09, 2018 at 03:07:00PM -0800, Raghavendra Rao Ananta wrote:
SNIP
>
> if (!task) {
> +#if defined CONFIG_HOTPLUG_CPU || defined CONFIG_KEXEC_CORE
> + struct perf_cpu_context *cpuctx =
> + container_of(ctx, struct perf_cpu_context, ctx);
> +
> + if (!cpuctx->online) {
> + perf_prepare_install_in_context(event);
> + return;
> + }
> +#endif
> cpu_function_call(cpu, __perf_install_in_context, event);
> return;
> }
> @@ -2421,6 +2443,43 @@ static int __perf_install_in_context(void *info)
> raw_spin_unlock_irq(&ctx->lock);
> }
>
> +#if defined CONFIG_HOTPLUG_CPU || defined CONFIG_KEXEC_CORE
> +static void perf_deferred_install_in_context(int cpu)
> +{
> + struct perf_event *event, *tmp;
> + struct perf_event_context *ctx;
> +
> + /* This function is called twice while coming online. Once for
> + * CPUHP_PERF_PREPARE and the other for CPUHP_AP_PERF_ONLINE.
> + * Only during the CPUHP_AP_PERF_ONLINE state, we can confirm
> + * that CPU PMU is ready and can be installed to.
> + */
> + if (!cpu_online(cpu))
> + return;
> +
> + spin_lock(&dormant_event_list_lock);
> + list_for_each_entry_safe(event, tmp, &dormant_event_list,
> + dormant_entry) {
> + if (cpu != event->cpu)
> + continue;
I wonder having per cpu lists would be better here,
could be quite busy for big number of CPUs
jirka
next prev parent reply other threads:[~2018-02-12 9:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 23:07 [PATCH] perf: Add support for creating offline events Raghavendra Rao Ananta
2018-02-12 9:43 ` Jiri Olsa
2018-02-12 17:42 ` Raghavendra Rao Ananta
2018-02-12 21:04 ` Jiri Olsa
2018-02-12 21:21 ` Jiri Olsa
2018-02-12 22:22 ` Raghavendra Rao Ananta
2018-02-13 16:08 ` Jiri Olsa
2018-02-13 18:03 ` Raghavendra Rao Ananta
2018-02-12 9:44 ` Jiri Olsa [this message]
2018-02-12 19:11 ` kbuild test robot
2018-02-13 18:23 ` Peter Zijlstra
2018-02-13 22:17 ` Sodagudi Prasad
2018-02-14 8:32 ` Peter Zijlstra
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=20180212094406.GE5821@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=psodagud@codeaurora.org \
--cc=rananta@codeaurora.org \
--cc=tsoni@codeaurora.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).