From: Guenter Roeck <linux@roeck-us.net>
To: Shu Wang <shuwang@redhat.com>
Cc: fenghua yu <fenghua.yu@intel.com>,
jdelvare@suse.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, chuhu@redhat.com,
yizhan@redhat.com, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] hwmon: (coretemp) remove duplicated coretemp for same core id
Date: Wed, 18 Oct 2017 22:25:57 -0700 [thread overview]
Message-ID: <20d0960f-e77a-8ee7-0205-707de46d034d@roeck-us.net> (raw)
In-Reply-To: <1715470689.17543079.1508380102988.JavaMail.zimbra@redhat.com>
On 10/18/2017 07:28 PM, Shu Wang wrote:
>> From: "Guenter Roeck" <linux@roeck-us.net>
>> To: "Shu Wang" <shuwang@redhat.com>
>> Cc: "fenghua yu" <fenghua.yu@intel.com>, jdelvare@suse.com, linux-hwmon@vger.kernel.org,
>> linux-kernel@vger.kernel.org, chuhu@redhat.com, yizhan@redhat.com
>> Sent: Wednesday, October 18, 2017 9:14:39 PM
>> Subject: Re: [PATCH] hwmon: (coretemp) remove duplicated coretemp for same core id
>>
>> On 10/17/2017 08:21 PM, Shu Wang wrote:
>>>> From: "Guenter Roeck" <linux@roeck-us.net>
>>>> To: shuwang@redhat.com
>>>> Cc: "fenghua yu" <fenghua.yu@intel.com>, jdelvare@suse.com,
>>>> linux-hwmon@vger.kernel.org,
>>>> linux-kernel@vger.kernel.org, chuhu@redhat.com, yizhan@redhat.com
>>>> Sent: Tuesday, October 17, 2017 11:25:50 PM
>>>> Subject: Re: [PATCH] hwmon: (coretemp) remove duplicated coretemp for same
>>>> core id
>>>>
>>>> On Tue, Oct 17, 2017 at 04:44:50PM +0800, shuwang@redhat.com wrote:
>>>>> From: Shu Wang <shuwang@redhat.com>
>>>>>
>>>>> Fix kernel warning on my 4cpus 2core_id system. The cpu0 and cpu1 have
>>>>> same core_id 0, so both cpu0 and cpu1 will try to create file temp2_label
>>>>> when it's online.
>>>>>
>>>> What system/cpu is that ?
>>>>
>>>> Normally I would assume that each CPU (package) instantiates
>>>> a separate instance of the driver.
>>>
>>> The system is ThinkPad X1 Carbon 3rd laptop, model 20BTS1N70F.
>>>
>>>>
>>>>> - coretemp_cpu_online(cpu=0)
>>>>> - create_core_data(cpu=0, attr_no=2)
>>>>> - create_core_attrs(attr_no=2)
>>>>> - coretemp_cpu_online(cpu=1)
>>>>> - create_core_data(cpu=1, attr_no=2)
>>>>> - create_core_attrs(attr_no=2)
>>>>>
>>>>> $ grep -e processor -e 'core id' /proc/cpuinfo
>>>>> processor : 0
>>>>> core id : 0
>>>>> processor : 1
>>>>> core id : 0
>>>>> processor : 2
>>>>> core id : 1
>>>>> processor : 3
>>>>> core id : 1
>>>>
>>>> Complete output of /proc/cpuinfo might be helpful.
>>>
>>> $ cat /proc/cpuinfo
>>> processor : 0
>>> vendor_id : GenuineIntel
>>> cpu family : 6
>>> model : 61
>>> model name : Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
>>
>> This is a hyperthreading CPU, which should already be handled,
>
> Do you mean that for my system, coretemp_cpu_online should only
> be called twice instead of four times to create two core attrs?
>
coretemp_add_core() should only be called twice, and cpumask_intersects()
should filter out the duplicate ones.
/*
* Check whether a thread sibling is already online. If not add the
* interface for this CPU core.
*/
if (!cpumask_intersects(&pdata->cpumask, topology_sibling_cpumask(cpu)))
coretemp_add_core(pdev, cpu, 0);
Thomas, is it possible that something is wrong with this code ?
Guenter
>> and the problem would affect pretty much everyone. I'll have
>> to look into this more closely. Is this with the ToT kernel ?
>
> What's a ToT kernel? The kernel I built was the latest
> kernel-4.14.0_rc5+ from linus repo.
>
ToT => Top Of Tree. My apologies, I thought that was a commonly used acronym.
Guenter
next prev parent reply other threads:[~2017-10-19 5:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 8:44 shuwang
2017-10-17 15:25 ` Guenter Roeck
2017-10-18 3:21 ` Shu Wang
2017-10-18 13:14 ` Guenter Roeck
2017-10-19 2:28 ` Shu Wang
2017-10-19 5:25 ` Guenter Roeck [this message]
2017-10-19 8:02 ` Thomas Gleixner
2017-10-19 10:10 ` Shu Wang
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=20d0960f-e77a-8ee7-0205-707de46d034d@roeck-us.net \
--to=linux@roeck-us.net \
--cc=chuhu@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shuwang@redhat.com \
--cc=tglx@linutronix.de \
--cc=yizhan@redhat.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
Powered by JetHome