From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Toshi Kani <toshi.kani@hp.com>, Dave Hansen <dave.hansen@intel.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: possible_cpus broken in linux-next
Date: Wed, 29 May 2013 21:02:20 +0200 [thread overview]
Message-ID: <51A650BC.7030604@intel.com> (raw)
In-Reply-To: <1369853414.16819.56.camel@misato.fc.hp.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8"; format="flowed", Size: 2199 bytes --]
On 5/29/2013 8:50 PM, Toshi Kani wrote:
> On Wed, 2013-05-29 at 12:35 -0600, Toshi Kani wrote:
>> On Wed, 2013-05-29 at 10:10 -0700, Dave Hansen wrote:
> :
>
>> Thanks for the report. The following patch fixes the problem.
>> -Toshi
>>
>> ====
>> From: Toshi Kani <toshi.kani@hp.com>
>> Subject: [PATCH] ACPI: Fix sysfs cpu/online of offlined cpus
> Typo. The subject needs to be:
>
> Subject: [PATCH] cpu: Fix sysfs cpu/online of offlined cpus
>
> -Toshi
>
>> As reported by Dave Hansen, sysfs cpu/online shows 1 for
>> offlined cpus at boot.
>> https://lkml.org/lkml/2013/5/29/403
>>
>> Fix this problem by initializing dev.offline with cpu_online()
>> when registering a cpu.
>>
>> Reported-by: Dave Hansen <dave.hansen@intel.com>
>> Signed-off-by: Toshi Kani <toshi.kani@hp.com>
Thanks Toshi!
Dave, can you please confirm that the problem is fixed by this patch?
Rafael
>> ---
>> drivers/base/cpu.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
>> index 130ba0b..b9f0eec 100644
>> --- a/drivers/base/cpu.c
>> +++ b/drivers/base/cpu.c
>> @@ -281,6 +281,7 @@ int __cpuinit register_cpu(struct cpu *cpu, int num)
>> cpu->dev.bus = &cpu_subsys;
>> cpu->dev.release = cpu_device_release;
>> cpu->dev.offline_disabled = !cpu->hotpluggable;
>> + cpu->dev.offline = !cpu_online(num);
>> #ifdef CONFIG_ARCH_HAS_CPU_AUTOPROBE
>> cpu->dev.bus->uevent = arch_cpu_uevent;
>> #endif
>
---------------------------------------------------------------------
Intel Technology Poland sp. z o.o.
z siedziba w Gdansku
ul. Slowackiego 173
80-298 Gdansk
Sad Rejonowy Gdansk Polnoc w Gdansku,
VII Wydzial Gospodarczy Krajowego Rejestru Sadowego,
numer KRS 101882
NIP 957-07-52-316
Kapital zakladowy 200.000 zl
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2013-05-29 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 17:10 possible_cpus broken in linux-next Dave Hansen
2013-05-29 18:35 ` Toshi Kani
2013-05-29 18:50 ` Toshi Kani
2013-05-29 19:02 ` Rafael J. Wysocki [this message]
2013-05-29 22:14 ` Dave Hansen
2013-05-29 22:46 ` Rafael J. Wysocki
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=51A650BC.7030604@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=dave.hansen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=toshi.kani@hp.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