From: Thomas Gleixner <tglx@linutronix.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Anju T Sudhakar <anju@linux.vnet.ibm.com>,
stewart@linux.vnet.ibm.com, ego@linux.vnet.ibm.com,
mikey@neuling.org, maddy@linux.vnet.ibm.com,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
eranian@google.com, hemant@linux.vnet.ibm.com,
Anton Blanchard <anton@samba.org>,
sukadev@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org,
dja@axtens.net
Subject: Re: [PATCH v8 05/10] powerpc/perf: IMC pmu cpumask and cpuhotplug support
Date: Thu, 11 May 2017 10:39:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1705111033500.1758@nanos> (raw)
In-Reply-To: <20170511094022.38a32f2e@canb.auug.org.au>
On Thu, 11 May 2017, Stephen Rothwell wrote:
> Hi,
>
> On Wed, 10 May 2017 14:09:53 +0200 (CEST) Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > > +static void nest_change_cpu_context(int old_cpu, int new_cpu)
> > > +{
> > > + int i;
> > > +
> > > + for (i = 0;
> > > + (per_nest_pmu_arr[i] != NULL) && (i < IMC_MAX_PMUS); i++)
> > > + perf_pmu_migrate_context(&per_nest_pmu_arr[i]->pmu,
> > > + old_cpu, new_cpu);
> >
> > Bah, this is horrible to read.
> >
> > struct imc_pmu **pn = per_nest_pmu_arr;
> > int i;
> >
> > for (i = 0; *pn && i < IMC_MAX_PMUS; i++, pn++)
> > perf_pmu_migrate_context(&(*pn)->pmu, old_cpu, new_cpu);
>
> (Just a bit of bike shedding ...)
>
> Or even (since "i" is not used any more):
>
> struct imc_pmu **pn;
>
> for (pn = per_nest_pmu_arr;
> pn < &per_nest_pmu_arr[IMC_MAX_PMUS] && *pn;
> pn++)
> perf_pmu_migrate_context(&(*pn)->pmu, old_cpu, new_cpu);
Which is equally unreadable as the original code I complained about. Is that
a corporate preference?
Thanks,
tglx
next prev parent reply other threads:[~2017-05-11 8:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 14:19 [PATCH v8 00/10] IMC Instrumentation Support Anju T Sudhakar
2017-05-04 14:19 ` [PATCH v8 01/10] powerpc/powernv: Data structure and macros definitions for IMC Anju T Sudhakar
2017-05-04 14:19 ` [PATCH v8 02/10] powerpc/powernv: Autoload IMC device driver module Anju T Sudhakar
2017-05-11 7:49 ` Stewart Smith
2017-05-12 4:36 ` Madhavan Srinivasan
2017-05-04 14:19 ` [PATCH v8 03/10] powerpc/powernv: Detect supported IMC units and its events Anju T Sudhakar
2017-05-04 14:19 ` [PATCH v8 04/10] powerpc/perf: Add generic IMC pmu groupand event functions Anju T Sudhakar
2017-05-04 14:19 ` [PATCH v8 05/10] powerpc/perf: IMC pmu cpumask and cpuhotplug support Anju T Sudhakar
2017-05-08 14:12 ` Daniel Axtens
2017-05-09 6:10 ` Madhavan Srinivasan
2017-05-12 2:18 ` Stewart Smith
2017-05-12 3:33 ` Michael Ellerman
2017-05-12 3:50 ` Madhavan Srinivasan
2017-05-12 3:41 ` Madhavan Srinivasan
2017-05-09 10:54 ` Anju T Sudhakar
2017-05-10 12:09 ` Thomas Gleixner
2017-05-10 23:40 ` Stephen Rothwell
2017-05-11 8:39 ` Thomas Gleixner [this message]
2017-05-15 10:12 ` Madhavan Srinivasan
2017-05-15 11:06 ` Thomas Gleixner
2017-05-04 14:19 ` [PATCH v8 06/10] powerpc/powernv: Core IMC events detection Anju T Sudhakar
2017-05-04 14:19 ` [PATCH v8 07/10] powerpc/perf: PMU functions for Core IMC and hotplugging Anju T Sudhakar
2017-05-17 7:57 ` Stewart Smith
2017-05-04 14:19 ` [PATCH v8 08/10] powerpc/powernv: Thread IMC events detection Anju T Sudhakar
2017-05-04 14:19 ` [PATCH v8 09/10] powerpc/perf: Thread IMC PMU functions Anju T Sudhakar
2017-05-04 14:19 ` [PATCH v8 10/10] powerpc/perf: Thread imc cpuhotplug support 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.1705111033500.1758@nanos \
--to=tglx@linutronix.de \
--cc=anju@linux.vnet.ibm.com \
--cc=anton@samba.org \
--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=peterz@infradead.org \
--cc=sfr@canb.auug.org.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®