linux-kernel - Re: [RFC PATCH v4 2/4] genirq/cpuhotplug: Dynamically isolate CPUs from managed interrupts

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 for Android: free password hash cracker in your pocket

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

Message-ID: <8734j3sfk8.ffs@tglx>
Date: Wed, 04 Dec 2024 15:12:07 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Costa Shulyupin <costa.shul@...hat.com>
Cc: longman@...hat.com, ming.lei@...hat.com, pauld@...hat.com,
 juri.lelli@...hat.com, vschneid@...hat.com, Tejun Heo <tj@...nel.org>,
 Johannes Weiner <hannes@...xchg.org>, Michal Koutný
 <mkoutny@...e.com>,
 linux-kernel@...r.kernel.org, cgroups@...r.kernel.org
Subject: Re: [RFC PATCH v4 2/4] genirq/cpuhotplug: Dynamically isolate CPUs
 from managed interrupts

On Wed, Dec 04 2024 at 15:56, Costa Shulyupin wrote:
> On Sun, 1 Dec 2024 at 15:43, Thomas Gleixner <tglx@...utronix.de> wrote:
> It is introduced by commit a46c27026da1 (blk-mq: don't schedule block
> kworker on isolated CPUs)
>
> I don't know what to do with the remaining drivers.

As long as that is not fixed, you obviously cannot change the semantics.

> I am exploring the possibility of improving CPU isolation from best-effort
> to guaranteed.

If all drivers are fixed then the interrupt enabled state itself becomes
irrelevant. If there is nothing which tickles them then they won't be
raised, no?

Thanks,

        tglx