From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 5/7] arm64: smp: remove cpu and numa topology information when hotplugging out CPU
Date: Tue, 17 Jul 2018 16:55:22 +0100 [thread overview]
Message-ID: <5a23f1c8-27cb-b09c-90fc-edab3eec99f9@arm.com> (raw)
In-Reply-To: <1c47b3fd-59ba-aba4-43b2-ed98e750887b@arm.com>
On 17/07/18 16:34, Sudeep Holla wrote:
>
>
> On 17/07/18 16:06, Geert Uytterhoeven wrote:
>> Hi Sudeep,
>>
>> On Tue, Jul 17, 2018 at 4:05 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
>>> On Tue, Jul 17, 2018 at 02:58:14PM +0200, Geert Uytterhoeven wrote:
>>>> On Fri, Jul 6, 2018 at 1:04 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> [...]
>
>>>> All but CPU0 tested, as expected.
>>>
>>> OK, does the firmware on this system not allow CPU0 to be hotplugged out ?
>>
>> Correct. But that's not the issue.
>>
>
> Yes, was just trying to understand the behavior.
>
> [..]
>
>>>> Woops, CPU5-7 are not tested.
>>>
>>> I don't understand what you mean by that. From the logs, it looks fine.
>>> What do you mean by "CPU5-7 are not tested" ?
>>> Sorry, but I am finding it hard to understand the issue from the log.
>>
>> The above is not the log, but the diff between the log before and after the bad
>> commit. So lines prefixed with "-" are no longer printed.
>> Before, CPU4-7 were tested for hotplug in group 1.
>> After, only CPU4 is tested for hotplug in group 1.
>>
>
> Ah OK, I think I now understand what is the issue, will try to replicate
> at my end and get back to you.
>
Going through the code again, I think I understand the problem here.
We use the topology_core_mask pointers which are stashed in cpu_groups[]
But, the cpumask themselves will be getting modified as the cpus go up
and down, so we need to make a copy instead of just using the pointer.
I will see what we can do to fix that.
--
Regards,
Sudeep
next prev parent reply other threads:[~2018-07-17 15:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 11:02 [PATCH v3 0/7] arm64: numa/topology/smp: update the cpumasks for CPU hotplug Sudeep Holla
2018-07-06 11:02 ` [PATCH v3 1/7] arm64: topology: refactor reset_cpu_topology to add support for removing topology Sudeep Holla
2018-07-06 11:02 ` [PATCH v3 2/7] arm64: numa: separate out updates to percpu nodeid and NUMA node cpumap Sudeep Holla
2018-07-06 11:02 ` [PATCH v3 3/7] arm64: topology: add support to remove cpu topology sibling masks Sudeep Holla
2018-07-06 11:02 ` [PATCH v3 4/7] arm64: topology: restrict updating siblings_masks to online cpus only Sudeep Holla
2018-07-06 11:02 ` [PATCH v3 5/7] arm64: smp: remove cpu and numa topology information when hotplugging out CPU Sudeep Holla
2018-07-17 12:58 ` Geert Uytterhoeven
2018-07-17 14:05 ` Sudeep Holla
2018-07-17 15:06 ` Geert Uytterhoeven
2018-07-17 15:34 ` Sudeep Holla
2018-07-17 15:55 ` Sudeep Holla [this message]
2018-07-17 17:01 ` Sudeep Holla
2018-07-18 7:15 ` Geert Uytterhoeven
2018-07-18 10:33 ` Sudeep Holla
2018-07-06 11:02 ` [PATCH v3 6/7] arm64: topology: rename llc_siblings to align with other struct members Sudeep Holla
2018-07-06 11:02 ` [PATCH v3 7/7] arm64: topology: re-introduce numa mask check for scheduler MC selection Sudeep Holla
2018-07-10 21:51 ` [PATCH v3 0/7] arm64: numa/topology/smp: update the cpumasks for CPU hotplug Jeremy Linton
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=5a23f1c8-27cb-b09c-90fc-edab3eec99f9@arm.com \
--to=sudeep.holla@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).