linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] arm64: numa/topology/smp: fix the cpumasks for CPU hotplug
Date: Tue, 12 Jun 2018 10:06:27 +0100	[thread overview]
Message-ID: <d6a7fc3c-fc3d-ac3c-cc6b-213e6da54598@arm.com> (raw)
In-Reply-To: <23796631-312b-82a0-fe03-cb7985433727@huawei.com>



On 12/06/18 02:14, Hanjun Guo wrote:
> Hi Sudeep,
> 
> On 2018/6/4 18:39, Sudeep Holla wrote:
>> Hi Will, Catalin, Jeremy, Morten,
>>
>> This is the fix I could come up for the issues we are seeing with arm64
>> for-next branch, in particular with commit 37c3ec2d810f ("arm64: topology:
>> divorce MC scheduling domain from core_siblings").
>>
>> The solution is to update the CPU topology during CPU hotplug operations
>> similar to other architectures like x86 and PPC. This is also inline
>> with the expection from the scheduler.
>>
>> I have cc-ed few Cavium and Huawei guys as they seem to have added or
>> modified the numa related code in the past.
> 
> Sorry for the late response, I can test on ARM64 NUMA systems
> with PPTT enabled, before I'm doing that, could you give some
> suggestion of the testing? what specific test case should I
> test? doing CPU offline/online when PPTT is enabled?
> 

Thanks for the response. I plan to post v2 after -rc1 which will have
some delta from this. So don't test this for now. Yes CPU hotplug tests
will be good. Also some NUMA based(numactl) assignments and try
hotplugging all CPUs in a node and similar tests with PPTT would be good.

-- 
Regards,
Sudeep

      reply	other threads:[~2018-06-12  9:06 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
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 [this message]

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=d6a7fc3c-fc3d-ac3c-cc6b-213e6da54598@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).