[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1b510c7e-6d48-4f3c-b3cb-8a7a0834784c@redhat.com>
Date: Fri, 17 Oct 2025 13:52:45 -0400
From: Waiman Long <llong@...hat.com>
To: Pingfan Liu <piliu@...hat.com>, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Tejun Heo <tj@...nel.org>, Johannes Weiner <hannes@...xchg.org>,
Michal Koutný <mkoutny@...e.com>,
Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>, Pierre Gondois <pierre.gondois@....com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>, Ben Segall <bsegall@...gle.com>,
Mel Gorman <mgorman@...e.de>, Valentin Schneider <vschneid@...hat.com>
Subject: Re: [PATCHv3] sched/deadline: Walk up cpuset hierarchy to decide root
domain when hot-unplug
On 10/17/25 8:26 AM, Pingfan Liu wrote:
> When testing kexec-reboot on a 144 cpus machine with
> isolcpus=managed_irq,domain,1-71,73-143 in kernel command line, I
> encounter the following bug:
>
> [ 97.114759] psci: CPU142 killed (polled 0 ms)
> [ 97.333236] Failed to offline CPU143 - error=-16
> [ 97.333246] ------------[ cut here ]------------
> [ 97.342682] kernel BUG at kernel/cpu.c:1569!
> [ 97.347049] Internal error: Oops - BUG: 00000000f2000800 [#1] SMP
> [ 97.353281] Modules linked in: rfkill sunrpc dax_hmem cxl_acpi cxl_port cxl_core einj vfat fat arm_smmuv3_pmu nvidia_cspmu arm_spe_pmu coresight_trbe arm_cspmu_module rndis_host ipmi_ssif cdc_ether i2c_smbus spi_nor usbnet ast coresight_tmc mii ixgbe i2c_algo_bit mdio mtd coresight_funnel coresight_stm stm_core coresight_etm4x coresight cppc_cpufreq loop fuse nfnetlink xfs crct10dif_ce ghash_ce sha2_ce sha256_arm64 sha1_ce sbsa_gwdt nvme nvme_core nvme_auth i2c_tegra acpi_power_meter acpi_ipmi ipmi_devintf ipmi_msghandler dm_mirror dm_region_hash dm_log dm_mod
> [ 97.404119] CPU: 0 UID: 0 PID: 2583 Comm: kexec Kdump: loaded Not tainted 6.12.0-41.el10.aarch64 #1
> [ 97.413371] Hardware name: Supermicro MBD-G1SMH/G1SMH, BIOS 2.0 07/12/2024
> [ 97.420400] pstate: 23400009 (nzCv daif +PAN -UAO +TCO +DIT -SSBS BTYPE=--)
> [ 97.427518] pc : smp_shutdown_nonboot_cpus+0x104/0x128
> [ 97.432778] lr : smp_shutdown_nonboot_cpus+0x11c/0x128
> [ 97.438028] sp : ffff800097c6b9a0
> [ 97.441411] x29: ffff800097c6b9a0 x28: ffff0000a099d800 x27: 0000000000000000
> [ 97.448708] x26: 0000000000000000 x25: 0000000000000000 x24: ffffb94aaaa8f218
> [ 97.456004] x23: ffffb94aaaabaae0 x22: ffffb94aaaa8f018 x21: 0000000000000000
> [ 97.463301] x20: ffffb94aaaa8fc10 x19: 000000000000008f x18: 00000000fffffffe
> [ 97.470598] x17: 0000000000000000 x16: ffffb94aa958fcd0 x15: ffff103acfca0b64
> [ 97.477894] x14: ffff800097c6b520 x13: 36312d3d726f7272 x12: ffff103acfc6ffa8
> [ 97.485191] x11: ffff103acf6f0000 x10: ffff103bc085c400 x9 : ffffb94aa88a0eb0
> [ 97.492488] x8 : 0000000000000001 x7 : 000000000017ffe8 x6 : c0000000fffeffff
> [ 97.499784] x5 : ffff003bdf62b408 x4 : 0000000000000000 x3 : 0000000000000000
> [ 97.507081] x2 : 0000000000000000 x1 : ffff0000a099d800 x0 : 0000000000000002
> [ 97.514379] Call trace:
> [ 97.516874] smp_shutdown_nonboot_cpus+0x104/0x128
> [ 97.521769] machine_shutdown+0x20/0x38
> [ 97.525693] kernel_kexec+0xc4/0xf0
> [ 97.529260] __do_sys_reboot+0x24c/0x278
> [ 97.533272] __arm64_sys_reboot+0x2c/0x40
> [ 97.537370] invoke_syscall.constprop.0+0x74/0xd0
> [ 97.542179] do_el0_svc+0xb0/0xe8
> [ 97.545562] el0_svc+0x44/0x1d0
> [ 97.548772] el0t_64_sync_handler+0x120/0x130
> [ 97.553222] el0t_64_sync+0x1a4/0x1a8
> [ 97.556963] Code: a94363f7 a8c47bfd d50323bf d65f03c0 (d4210000)
> [ 97.563191] ---[ end trace 0000000000000000 ]---
> [ 97.595854] Kernel panic - not syncing: Oops - BUG: Fatal exception
> [ 97.602275] Kernel Offset: 0x394a28600000 from 0xffff800080000000
> [ 97.608502] PHYS_OFFSET: 0x80000000
> [ 97.612062] CPU features: 0x10,0000000d,002a6928,5667fea7
> [ 97.617580] Memory Limit: none
> [ 97.648626] ---[ end Kernel panic - not syncing: Oops - BUG: Fatal exception ]
>
> Tracking down this issue, I found that dl_bw_deactivate() returned
> -EBUSY, which caused sched_cpu_deactivate() to fail on the last CPU.
> When a CPU is inactive, its rd is set to def_root_domain. For an
> blocked-state deadline task (in this case, "cppc_fie"), it was not
> migrated to CPU0, and its task_rq() information is stale. As a result,
> its bandwidth is wrongly accounted into def_root_domain during domain
> rebuild.
First of all, in an emergency situation when we need to shutdown the
kernel, does it really matter if dl_bw_activate() returns -EBUSY? Should
we just go ahead and ignore this dl_bw generated error?
> The key point is that root_domain is only tracked through active rq->rd.
> To avoid using a global data structure to track all root_domains in the
> system, we need a way to locate an active CPU within the corresponding
> root_domain.
>
> The following rules stand for deadline sub-system and help locating the
> active cpu
> -1.any cpu belongs to a unique root domain at a given time
> -2.DL bandwidth checker ensures that the root domain has active cpus.
>
> Now, let's examine the blocked-state task P.
> If P is attached to a cpuset that is a partition root, it is
> straightforward to find an active CPU.
> If P is attached to a cpuset that has changed from 'root' to 'member',
> the active CPUs are grouped into the parent root domain. Naturally, the
> CPUs' capacity and reserved DL bandwidth are taken into account in the
> ancestor root domain. (In practice, it may be unsafe to attach P to an
> arbitrary root domain, since that domain may lack sufficient DL
> bandwidth for P.) Again, it is straightforward to find an active CPU in
> the ancestor root domain.
>
> This patch groups CPUs into isolated and housekeeping sets. For the
> housekeeping group, it walks up the cpuset hierarchy to find active CPUs
> in P's root domain and retrieves the valid rd from cpu_rq(cpu)->rd.
>
> Signed-off-by: Pingfan Liu <piliu@...hat.com>
> Cc: Waiman Long <longman@...hat.com>
> Cc: Tejun Heo <tj@...nel.org>
> Cc: Johannes Weiner <hannes@...xchg.org>
> Cc: "Michal Koutný" <mkoutny@...e.com>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: Peter Zijlstra <peterz@...radead.org>
> Cc: Juri Lelli <juri.lelli@...hat.com>
> Cc: Pierre Gondois <pierre.gondois@....com>
> Cc: Vincent Guittot <vincent.guittot@...aro.org>
> Cc: Dietmar Eggemann <dietmar.eggemann@....com>
> Cc: Steven Rostedt <rostedt@...dmis.org>
> Cc: Ben Segall <bsegall@...gle.com>
> Cc: Mel Gorman <mgorman@...e.de>
> Cc: Valentin Schneider <vschneid@...hat.com>
> To: cgroups@...r.kernel.org
> To: linux-kernel@...r.kernel.org
> ---
> include/linux/cpuset.h | 18 ++++++++++++++++++
> kernel/cgroup/cpuset.c | 27 +++++++++++++++++++++++++++
> kernel/sched/deadline.c | 30 ++++++++++++++++++++++++------
> 3 files changed, 69 insertions(+), 6 deletions(-)
>
> diff --git a/include/linux/cpuset.h b/include/linux/cpuset.h
> index 2ddb256187b51..7c00ebcdf85d9 100644
> --- a/include/linux/cpuset.h
> +++ b/include/linux/cpuset.h
> @@ -130,6 +130,7 @@ extern void rebuild_sched_domains(void);
>
> extern void cpuset_print_current_mems_allowed(void);
> extern void cpuset_reset_sched_domains(void);
> +extern void task_get_rd_effective_cpus(struct task_struct *p, struct cpumask *cpus);
>
> /*
> * read_mems_allowed_begin is required when making decisions involving
> @@ -276,6 +277,23 @@ static inline void cpuset_reset_sched_domains(void)
> partition_sched_domains(1, NULL, NULL);
> }
>
> +static inline void task_get_rd_effective_cpus(struct task_struct *p,
> + struct cpumask *cpus)
> +{
> + const struct cpumask *hk_msk;
> + struct cpumask msk;
> +
> + hk_msk = housekeeping_cpumask(HK_TYPE_DOMAIN);
> + if (housekeeping_enabled(HK_TYPE_DOMAIN)) {
> + if (!cpumask_and(&msk, p->cpus_ptr, hk_msk)) {
> + /* isolated cpus belong to a root domain */
> + cpumask_andnot(cpus, cpu_active_mask, hk_msk);
> + return;
> + }
> + }
> + cpumask_and(cpus, cpu_active_mask, hk_msk);
> +}
The size of struct cpumask can be large depending on the extra value of
NR_CPUS. For a x86-64 RHEL kernel, it is over 1 kbytes. We can actually
eliminate the use of a struct cpumask variable by replacing
cpumask_and() with cpumask_intersects().
You said that isolated CPUs belong to a root domain. In the case of CPUs
within an isolated partition, the CPUs are in a null root domain which I
don't know if it is problematic or not.
We usually prefix an externally visible function from cpuset with the
cpuset prefix to avoid namespace collision. You should consider doing
that for this function.
Also I am still not very clear about the exact purpose of this function.
You should probably add comment about this.
> +
> static inline void cpuset_print_current_mems_allowed(void)
> {
> }
> diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
> index 27adb04df675d..f7b18892ed093 100644
> --- a/kernel/cgroup/cpuset.c
> +++ b/kernel/cgroup/cpuset.c
> @@ -1102,6 +1102,33 @@ void cpuset_reset_sched_domains(void)
> mutex_unlock(&cpuset_mutex);
> }
>
> +/* caller hold RCU read lock */
> +void task_get_rd_effective_cpus(struct task_struct *p, struct cpumask *cpus)
> +{
> + const struct cpumask *hk_msk;
> + struct cpumask msk;
> + struct cpuset *cs;
> +
> + hk_msk = housekeeping_cpumask(HK_TYPE_DOMAIN);
> + if (housekeeping_enabled(HK_TYPE_DOMAIN)) {
> + if (!cpumask_and(&msk, p->cpus_ptr, hk_msk)) {
> + /* isolated cpus belong to a root domain */
> + cpumask_andnot(cpus, cpu_active_mask, hk_msk);
> + return;
> + }
> + }
> + /* In HK_TYPE_DOMAIN, cpuset can be applied */
> + cs = task_cs(p);
> + while (cs != &top_cpuset) {
> + if (is_sched_load_balance(cs))
> + break;
> + cs = parent_cs(cs);
> + }
> +
> + /* For top_cpuset, its effective_cpus does not exclude isolated cpu */
> + cpumask_and(cpus, cs->effective_cpus, hk_msk);
> +}
> +
Similar problems with the non-CONFIG_CPUSETS version in cpuset.h.
Cheers,
Longman
Powered by blists - more mailing lists