linux-kernel - [Question] Include isolated cpu to ensure that tasks are not scheduled to isolated cpu？

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <3e68ccda-1606-9494-f57a-75be9668b83d@huawei.com>
Date: Mon, 2 Sep 2024 09:56:51 +0800
From: zhengzucheng <zhengzucheng@...wei.com>
To: <peterz@...radead.org>, <juri.lelli@...hat.com>,
	<vincent.guittot@...aro.org>, <dietmar.eggemann@....com>,
	<rostedt@...dmis.org>, <bsegall@...gle.com>, <mgorman@...e.de>,
	<bristot@...hat.com>, <vschneid@...hat.com>, <oleg@...hat.com>, Frederic
 Weisbecker <frederic@...nel.org>, <mingo@...nel.org>, <peterx@...hat.com>,
	<tj@...nel.org>, <longman@...hat.com>
CC: <linux-kernel@...r.kernel.org>
Subject: [Question] Include isolated cpu to ensure that tasks are not scheduled to isolated cpu？

In a cpuset subsystem, cpuset.cpus contains isolated cpu and 
non-isolated cpu.
Is there any way to ensure that the task runs only on the non-isolated cpus?
eg：
isolcpus=1, cpusete.cpus=0-7. It is found that some tasks are scheduled 
to cpu1.

In addition, task run on isolated cpu cann't be scheduled to other cpu 
in the future.

Thanks!