linux-kernel - Re: [PATCH] sched/fair: Fix ksmd and kthreadd running on isolated CPU0 on arm64 systems

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <tencent_C5D662949D58221F89531E4CC3CE72879507@qq.com>
Date: Mon,  6 Jan 2025 17:48:40 +0800
From: wujing <realwujing@...com>
To: peterz@...radead.org
Cc: gregkh@...uxfoundation.org,
	linux-kernel@...r.kernel.org,
	mingo@...hat.com,
	realwujing@...com,
	sasha.levin@...ux.microsoft.com,
	stable@...r.kernel.org,
	yuanql9@...natelecom.cn
Subject: Re: [PATCH] sched/fair: Fix ksmd and kthreadd running on isolated CPU0 on arm64 systems

The reason this issue does not occur on x86 architecture is that x86 does not 
use the `select_idle_cpu` function for core selection. Instead, it uses the
`select_idle_smt` function. However, there is still an issue on x86 where 
isolated cores are not properly excluded. My other commit, 
`sched/fair: Correct CPU selection from isolated domain`, addresses the issue 
of isolated cores on x86.

> Your subject explicitly mentions arm64, however there is absolutely
> nothing arm64 specific to this patch, as such the subject is just plain
> wrong.