linux-kernel - Re: [PATCH v2 0/5] x86/percpu semantics and fixes

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

Message-ID: <ED22D686-D425-43B9-A3FB-ED4A54B1C4DF@vmware.com>
Date:   Thu, 13 Jun 2019 18:49:49 +0000
From:   Nadav Amit <namit@...are.com>
To:     Peter Zijlstra <peterz@...radead.org>
CC:     Linus Torvalds <torvalds@...ux-foundation.org>,
        "mingo@...nel.org" <mingo@...nel.org>,
        "bp@...en8.de" <bp@...en8.de>,
        "tglx@...utronix.de" <tglx@...utronix.de>,
        "luto@...nel.org" <luto@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/5] x86/percpu semantics and fixes

> On Jun 13, 2019, at 6:54 AM, Peter Zijlstra <peterz@...radead.org> wrote:
> 
> Hi all,
> 
> I still have these patches sitting in my queue and figured I'd repost them.
> 
> Last time Linus proposed a "+m" alternative approach, but that generates far
> far worse code (I've lost the patch and not re-ran those numbers, but I suppose
> I can redo if found important).

I remember I tried it as well and got the same results.

> These patches have been through 0day for a while.

Finally, I would not need to cache smp_processor_id() on the stack when it
is used multiple times…