From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Dave Hansen <dave@sr71.net>
Cc: Toshi Kani <toshi.kani@hp.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: cpu hotplug: possible_cpus broken (again?) next-20130607
Date: Wed, 12 Jun 2013 00:34:51 +0200 [thread overview]
Message-ID: <27437213.QrmAtijARn@vostro.rjw.lan> (raw)
In-Reply-To: <51B7A1F8.6080507@sr71.net>
On Tuesday, June 11, 2013 03:17:28 PM Dave Hansen wrote:
> On 06/11/2013 03:05 PM, Rafael J. Wysocki wrote:
> > On Tuesday, June 11, 2013 02:51:33 PM Dave Hansen wrote:
> >> possible_cpus looks broken again. I'm booting with:
> >>
> >> maxcpus=10 possible_cpus=160
> >>
> >> But I only get 0-9 in sysfs:
> >>
> >>> # ls /sys/devices/system/cpu/
> >>> cpu0 cpu2 cpu4 cpu6 cpu8 cpufreq kernel_max offline possible probe uevent
> >>> cpu1 cpu3 cpu5 cpu7 cpu9 cpuidle modalias online present release
> >
> > Can you please test the acpi-hotplug branch of the linux-pm.git tree?
>
> That branch seems to work happily.
In that case the problem may have been reintroduced by a merge conflict fix in
linux-next.
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-06-11 22:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 21:51 Dave Hansen
2013-06-11 22:05 ` Rafael J. Wysocki
2013-06-11 22:17 ` Dave Hansen
2013-06-11 22:34 ` Rafael J. Wysocki [this message]
2013-06-11 22:32 ` Toshi Kani
2013-06-12 12:03 ` Youquan Song
2013-06-12 0:24 ` Dave Hansen
2013-06-12 12:32 ` Youquan Song
2013-06-12 4:07 ` Yinghai Lu
2013-06-12 11:02 ` Rafael J. Wysocki
2013-06-13 1:36 ` Youquan Song
2013-06-13 15:36 ` Toshi Kani
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=27437213.QrmAtijARn@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=dave@sr71.net \
--cc=gregkh@linuxfoundation.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
all inboxes | Powered by JetHome®