linux-kernel - Re: [RFC PATCH 3/3] MIPS: io.h: Remove barriers before MMIO accessors for CPU without WB

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: <alpine.DEB.2.21.2202211612440.56785@angie.orcam.me.uk>
Date:   Mon, 21 Feb 2022 16:43:07 +0000 (GMT)
From:   "Maciej W. Rozycki" <macro@...am.me.uk>
To:     Jiaxun Yang <jiaxun.yang@...goat.com>
cc:     linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
        chenhuacai@...nel.org, tsbogend@...ha.franken.de
Subject: Re: [RFC PATCH 3/3] MIPS: io.h: Remove barriers before MMIO accessors
 for CPU without WB

On Mon, 21 Feb 2022, Jiaxun Yang wrote:

> Commit 3d474da ("MIPS: Enforce strong ordering for MMIO accessors")

 Please follow the canonical commit reference format including a 12-digit 
hexadecimal hash reference (`scripts/checkpatch.pl' would have pointed it 
out).

> SYNC based barrier is very heavy on Loongson and MTI cores as it will
> issue a SYNC command on their bus and invalidate all present instrutions
> in pipeline. We should generally avoid that.

 Use whatever lighterweight barrier instruction you have available for 
your specific platforms then that fulfills the ordering enforcement 
required here for your specific platforms of concern that you have 
identified and know well rather than across the board.  The reason for 
this is this is an optimisation and the default barrier model needs to 
ensure correct execution with any implementation.

  Maciej