From: jhugo@codeaurora.org (Jeffrey Hugo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] arm64: topology: refactor reset_cpu_topology to add support for removing topology
Date: Mon, 4 Jun 2018 08:58:14 -0600 [thread overview]
Message-ID: <9f76f11f-d77b-ae39-f06b-97ab1b981e31@codeaurora.org> (raw)
In-Reply-To: <1528108797-13743-2-git-send-email-sudeep.holla@arm.com>
On 6/4/2018 4:39 AM, Sudeep Holla wrote:
> Currently reset_cpu_topology clears all the CPU topology information
> and resets to default values. However we may need to just clear the
> information when we hotplig out the CPU. In preparation to add the
hotplug
> support the same, let's refactor reset_cpu_topology to clear out the
> information and reset them only if explicitly requested.
>
--
Jeffrey Hugo
Qualcomm Datacenter Technologies as an affiliate of Qualcomm
Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2018-06-04 14:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 10:39 [PATCH 0/5] arm64: numa/topology/smp: fix the cpumasks for CPU hotplug Sudeep Holla
2018-06-04 10:39 ` [PATCH 1/5] arm64: topology: refactor reset_cpu_topology to add support for removing topology Sudeep Holla
2018-06-04 14:58 ` Jeffrey Hugo [this message]
2018-06-04 10:39 ` [PATCH 2/5] arm64: topology: add support to remove cpu topology Sudeep Holla
2018-06-04 10:39 ` [PATCH 3/5] arm64: numa: separate out updates to percpu nodeid and NUMA node cpumap Sudeep Holla
2018-06-04 10:39 ` [PATCH 4/5] arm64: smp: remove cpu and numa topology information when hotplugging out CPU Sudeep Holla
2018-06-04 10:39 ` [PATCH 5/5] arm64: topology: rename llc_siblings to align with other struct members Sudeep Holla
2018-06-12 1:14 ` [PATCH 0/5] arm64: numa/topology/smp: fix the cpumasks for CPU hotplug Hanjun Guo
2018-06-12 9:06 ` Sudeep Holla
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=9f76f11f-d77b-ae39-f06b-97ab1b981e31@codeaurora.org \
--to=jhugo@codeaurora.org \
--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).