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>] [day] [month] [year] [list]
Message-ID: <a6a073ef-e208-44cb-b41f-85c29c42ee9c@usask.ca>
Date: Thu, 24 Oct 2024 13:04:04 -0600
From: Chris Friesen <cbf123@...sk.ca>
To: LKML <linux-kernel@...r.kernel.org>
Subject: is there any dynamic equivalent to the "isolcpus=managed_irq" boot
 arg?

Hi all,

In the kernel boot args we can specify something like 
"isolcpus=managed_irq,nohz,domain,<cpu-list>" to tell the kernel to 
isolate a given set of CPUs and *also* prevent them from being targeted 
by managed interrupts.

The boot-time isolcpus mechanism is deprecated, so is there a runtime 
equivalent to tell the kernel to avoid certain CPUs for managed 
interrupts?   I just stumbled over https://lkml.org/lkml/2024/9/16/563 
which makes me think the answer might be that no such mechanism exists 
currently.

I'm not subscribed to the list so please CC me on replies.

Thanks,
Chris Friesen



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ