linux-kernel - Re: [tip: irq/core] x86: Select HARDIRQS_SW

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: <CACRpkdb7vxSaK1Df6gNX_Kq-LF=S1qx2iKdmBy1Ku0vEpDVPbA@mail.gmail.com>
Date:   Thu, 12 Mar 2020 15:02:49 +0100
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Hans de Goede <hdegoede@...hat.com>
Cc:     "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        linux-tip-commits@...r.kernel.org,
        Thomas Gleixner <tglx@...utronix.de>, x86 <x86@...nel.org>
Subject: Re: [tip: irq/core] x86: Select HARDIRQS_SW_RESEND on x86

On Thu, Mar 12, 2020 at 2:49 PM Hans de Goede <hdegoede@...hat.com> wrote:

[Me]
> > I see that ARM and ARM64 simply just select this. What
> > happens if you do that and why is x86 not selecting it in general?
>
> Erm, "selecting it in general" (well at least on x86) is what
> this patch is doing.

Sorry that I was unclear, what I meant to say is why wasn't
this done ages ago since so many important architectures seem
to have it enabled by default.

I suppose the reason would be something like "firmware/BIOS
should handle that for us" and recently that has started to
break apart and x86 platforms started to be more like ARM?

Yours,
Linus Walleij