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]
Date:   Thu, 11 Apr 2019 15:34:33 -0700
From:   Linus Torvalds <>
To:     Benjamin Herrenschmidt <>
Cc:     Will Deacon <>,
        linux-arch <>,
        Linux List Kernel Mailing <>,
        "Paul E. McKenney" <>,
        Michael Ellerman <>,
        Arnd Bergmann <>,
        Peter Zijlstra <>,
        Andrea Parri <>,
        Palmer Dabbelt <>,
        Daniel Lustig <>,
        David Howells <>,
        Alan Stern <>,
        "Maciej W. Rozycki" <>,
        Paul Burton <>,
        Ingo Molnar <>,
        Yoshinori Sato <>,
        Rich Felker <>, Tony Luck <>,
        Mikulas Patocka <>,
        Akira Yokosawa <>,
        Luis Chamberlain <>,
        Nicholas Piggin <>
Subject: Re: [PATCH v2 01/21] docs/memory-barriers.txt: Rewrite "KERNEL I/O

On Thu, Apr 11, 2019 at 3:13 PM Benjamin Herrenschmidt
<> wrote:
> Minor nit... I would have said "All readX() and writeX() accesses _from
> the same CPU_ to the same peripheral... and then s/the CPU/this CPU.

Maybe talk about "same thread" rather than "same cpu", with the
understanding that scheduling/preemption has to include the
appropriate cross-CPU IO barrier?


Powered by blists - more mailing lists