From: Ingo Molnar <mingo@kernel.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
linux-hwmon@vger.kernel.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, corbet@lwn.net, fenghua.yu@intel.com,
jdelvare@suse.com, linux@roeck-us.net, len.brown@intel.com
Subject: Re: [PATCH 3/7] hwmon/coretemp: Handle large core id value
Date: Sun, 14 Aug 2022 11:12:08 +0200 [thread overview]
Message-ID: <Yvi8aBtytJ1pEDoe@gmail.com> (raw)
In-Reply-To: <e5a8d07eda23baf07a89ebf54b70d1cfab183837.camel@intel.com>
* Zhang Rui <rui.zhang@intel.com> wrote:
> On Sat, 2022-08-13 at 12:48 +0200, Ingo Molnar wrote:
> >
> > * Zhang Rui <rui.zhang@intel.com> wrote:
> >
> > > The coretemp driver supports up to a hard-coded limit of 128 cores.
> > >
> > > Today, the driver can not support a core with an id above that
> > > limit.
> > > Yet, the encoding of core_id's is arbitrary (BIOS APIC-id) and so
> > > they
> > > may be sparse and they may be large.
> > >
> > > Update the driver to map arbitrary core_id numbers into appropriate
> > > array indexes so that 128 cores can be supported, no matter the
> > > encoding
> > > of core_ids's.
> >
> > Please capitalize 'ID' consistently throughout the series.
> >
> > > - attr_no = pkg_flag ? PKG_SYSFS_ATTR_NO : TO_ATTR_NO(cpu);
> > > + if (pkg_flag)
> > > + attr_no = PKG_SYSFS_ATTR_NO;
> > > + else {
> > > + index = ida_alloc(&pdata->ida, GFP_KERNEL);
> > > + if (index < 0)
> > > + return index;
> > > + pdata->cpu_map[index] = topology_core_id(cpu);
> > > + attr_no = index + BASE_SYSFS_ATTR_NO;
> > > + }
> >
> > Unbalanced curly braces.
>
> Sure, will fix these two issues in next version.
>
> >
> > > - int err, attr_no;
> > > + int err, index, attr_no;
> >
> > So it's 'index' here.
> >
> > > @@ -524,6 +538,8 @@ static void coretemp_remove_core(struct
> > > platform_data *pdata, int indx)
> >
> > But 'indx' here.
> >
> > > - int indx, target;
> > > + int i, indx = -1, target;
> >
> > And 'indx' again. Did we run out of the letter 'e'? Either use
> > 'index'
> > naming consistently, or 'idx' if it has to be abbreviated.
>
> I'd prefer 'index', but here, this 'indx' is from previous code and
> this patch just initializes it to -1.
Then queue up a cleanup patch as patch #1 - but idiosyncratic noise like
that makes review harder.
Thanks,
Ingo
next prev parent reply other threads:[~2022-08-14 9:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 16:41 [PATCH 0/7] x86/topology: Improve CPUID.1F handling Zhang Rui
2022-08-12 16:41 ` [PATCH 1/7] x86/topology: Fix multiple packages shown on a single-package system Zhang Rui
2022-08-12 16:41 ` [PATCH 2/7] x86/topology: Fix duplicated core_id within a package Zhang Rui
2022-08-12 16:41 ` [PATCH 3/7] hwmon/coretemp: Handle large core id value Zhang Rui
2022-08-12 17:16 ` Guenter Roeck
2022-08-13 17:24 ` Zhang Rui
2022-08-13 10:48 ` Ingo Molnar
2022-08-13 17:07 ` Zhang Rui
2022-08-14 9:12 ` Ingo Molnar [this message]
2022-08-12 16:41 ` [PATCH 4/7] x86/topology: Fix max_siblings calculation Zhang Rui
2022-08-12 16:41 ` [PATCH 5/7] Documentation: x86: Update smp_num_siblings/x86_max_cores description Zhang Rui
2022-08-12 16:41 ` [PATCH 6/7] Documentation: x86: Remove obsolete x86_max_dies description Zhang Rui
2022-08-12 16:41 ` [PATCH 7/7] perf/x86/intel/P4: Fix smp_num_siblings usage Zhang Rui
2022-08-13 10:50 ` Ingo Molnar
2022-08-13 17:29 ` Zhang Rui
2022-08-15 9:11 ` Peter Zijlstra
2022-08-16 2:26 ` Zhang Rui
2022-08-16 8:26 ` Peter Zijlstra
2022-08-13 10:44 ` [PATCH 0/7] x86/topology: Improve CPUID.1F handling Ingo Molnar
2022-08-13 17:10 ` Zhang Rui
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=Yvi8aBtytJ1pEDoe@gmail.com \
--to=mingo@kernel.org \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jdelvare@suse.com \
--cc=len.brown@intel.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mingo@redhat.com \
--cc=rui.zhang@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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