From: Thomas Gleixner <tglx@linutronix.de>
To: Anju T Sudhakar <anju@linux.vnet.ibm.com>
Cc: mpe@ellerman.id.au, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, ego@linux.vnet.ibm.com,
bsingharora@gmail.com, anton@samba.org,
sukadev@linux.vnet.ibm.com, mikey@neuling.org,
stewart@linux.vnet.ibm.com, dja@axtens.net, eranian@google.com,
hemant@linux.vnet.ibm.com, maddy@linux.vnet.ibm.com
Subject: Re: [PATCH v9 10/10] powerpc/perf: Thread imc cpuhotplug support
Date: Tue, 6 Jun 2017 12:27:38 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1706061209140.1885@nanos> (raw)
In-Reply-To: <1496665922-702-3-git-send-email-anju@linux.vnet.ibm.com>
On Mon, 5 Jun 2017, Anju T Sudhakar wrote:
> static void thread_imc_mem_alloc(int cpu_id)
> {
> - u64 ldbar_addr, ldbar_value;
> int phys_id = topology_physical_package_id(cpu_id);
>
> per_cpu_add[cpu_id] = (u64)alloc_pages_exact_nid(phys_id,
> (size_t)IMC_THREAD_COUNTER_MEM, GFP_KERNEL | __GFP_ZERO);
It took me a while to understand that per_cpu_add is an array and not a new
fangled per cpu function which adds something to a per cpu variable.
So why is that storing the address as u64?
And why is this a NR_CPUS sized array instead of a regular per cpu variable?
> +}
> +
> +static void thread_imc_update_ldbar(unsigned int cpu_id)
> +{
> + u64 ldbar_addr, ldbar_value;
> +
> + if (per_cpu_add[cpu_id] == 0)
> + thread_imc_mem_alloc(cpu_id);
So if that allocation fails then you happily proceed. Optmistic
programming, right?
> +
> ldbar_addr = (u64)virt_to_phys((void *)per_cpu_add[cpu_id]);
Ah, it's stored as u64 because you have to convert it back to a void
pointer at the place where it is actually used. Interesting approach.
> ldbar_value = (ldbar_addr & (u64)THREAD_IMC_LDBAR_MASK) |
> - (u64)THREAD_IMC_ENABLE;
> + (u64)THREAD_IMC_ENABLE;
> mtspr(SPRN_LDBAR, ldbar_value);
> }
>
> @@ -442,6 +450,26 @@ static void core_imc_change_cpu_context(int old_cpu, int new_cpu)
> perf_pmu_migrate_context(&core_imc_pmu->pmu, old_cpu, new_cpu);
> }
>
> +static int ppc_thread_imc_cpu_online(unsigned int cpu)
> +{
> + thread_imc_update_ldbar(cpu);
> + return 0;
> +}
> +
> +static int ppc_thread_imc_cpu_offline(unsigned int cpu)
> +{
> + mtspr(SPRN_LDBAR, 0);
> + return 0;
> +}
> +
> +void thread_imc_cpu_init(void)
> +{
> + cpuhp_setup_state(CPUHP_AP_PERF_POWERPC_THREAD_IMC_ONLINE,
> + "perf/powerpc/imc_thread:online",
> + ppc_thread_imc_cpu_online,
> + ppc_thread_imc_cpu_offline);
> +}
> +
> static int ppc_core_imc_cpu_online(unsigned int cpu)
> {
> const struct cpumask *l_cpumask;
> @@ -953,6 +981,9 @@ int __init init_imc_pmu(struct imc_events *events, int idx,
> if (ret)
> return ret;
> break;
> + case IMC_DOMAIN_THREAD:
> + thread_imc_cpu_init();
> + break;
> default:
> return -1; /* Unknown domain */
> }
Just a general observation. If anything in init_imc_pmu() fails, then all
the hotplug callbacks are staying registered, at least I haven't seen
anything undoing it.
Thanks,
tglx
next prev parent reply other threads:[~2017-06-06 10:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 12:32 [PATCH v9 05/10] powerpc/perf: IMC pmu cpumask and " Anju T Sudhakar
2017-06-05 12:32 ` [PATCH v9 07/10] powerpc/perf: PMU functions for Core IMC and hotplugging Anju T Sudhakar
2017-06-06 10:09 ` Thomas Gleixner
2017-06-07 5:44 ` Anju T Sudhakar
2017-06-07 10:34 ` Anju T Sudhakar
2017-06-12 22:44 ` Thomas Gleixner
2017-06-05 12:32 ` [PATCH v9 10/10] powerpc/perf: Thread imc cpuhotplug support Anju T Sudhakar
2017-06-06 10:27 ` Thomas Gleixner [this message]
2017-06-08 18:05 ` Madhavan Srinivasan
2017-06-06 8:39 ` [PATCH v9 05/10] powerpc/perf: IMC pmu cpumask and " Thomas Gleixner
2017-06-07 5:26 ` Anju T Sudhakar
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=alpine.DEB.2.20.1706061209140.1885@nanos \
--to=tglx@linutronix.de \
--cc=anju@linux.vnet.ibm.com \
--cc=anton@samba.org \
--cc=bsingharora@gmail.com \
--cc=dja@axtens.net \
--cc=ego@linux.vnet.ibm.com \
--cc=eranian@google.com \
--cc=hemant@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=stewart@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.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
all inboxes | Powered by JetHome®