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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Dec 04 2024 at 15:56, Costa Shulyupin wrote:
> On Sun, 1 Dec 2024 at 15:43, Thomas Gleixner <tglx@xxxxxxxxxxxxx> 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




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]     [Monitors]

  Powered by Linux