[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51266721.5060006@codeaurora.org>
Date: Thu, 21 Feb 2013 10:27:45 -0800
From: Stephen Boyd <sboyd@...eaurora.org>
To: Nathan Zimmer <nzimmer@....com>
CC: akpm@...ux-foundation.org, mm-commits@...r.kernel.org,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: mmotm 2013-02-19-17-20 uploaded
On 2/21/2013 10:18 AM, Nathan Zimmer wrote:
> On Thu, Feb 21, 2013 at 01:25:29AM -0800, Stephen Boyd wrote:
>> On 2/19/2013 5:21 PM, akpm@...ux-foundation.org wrote:
>>> * timer_list-split-timer_list_show_tickdevices.patch
>>> * timer_list-convert-timer-list-to-be-a-proper-seq_file.patch
>>> * timer_list-convert-timer-list-to-be-a-proper-seq_file-fix.patch
>>> * timer_list-convert-timer-list-to-be-a-proper-seq_file-v2.patch
>>> * timer_list-convert-timer-list-to-be-a-proper-seq_file-v2-fix.patch
>>> * timer_list-convert-timer-list-to-be-a-proper-seq_file-fix-fix.patch
>> These commits seem to break the timer list on devices with maxcpus !=
>> nr_cpu_ids, which is possible if you specify maxcpus on the kernel
>> command line. I no longer see the percpu devices that I normally have
>> after the broadcast device.
> Interesting.
> However I can't seem to boot at the moment with maxcpus set to less then the actual
> number of cpus so I am not having much luck investigating right now.
It works well on ARM processors. I believe it still works on x86 devices
as well. I suppose you can simulate it by offlining a CPU and then
reading the file.
This comment is useful around the cpumask functions.
Returns >= nr_cpu_ids if no further cpus set.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists