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  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:   Fri, 8 Mar 2019 23:56:03 +0000 (GMT)
From:   "Maciej W. Rozycki" <>
To:     Alexandre Oliva <>
cc:     Aaro Koskinen <>, Tom Li <>,
        James Hogan <>,
        Jiaxun Yang <>,
        Huacai Chen <>,
        Ralf Baechle <>,,
Subject: Re: [RFC] On the Current Troubles of Mainlining Loongson Platform

On Thu, 7 Mar 2019, Alexandre Oliva wrote:

> > Does your platform use `war_io_reorder_wmb'?
> Err...  I'm not sure I understand your question.
> It uses it in __BUILD_IOPORT_SINGLE within the expanded out function,
> given !barrier, but you already knew that.
> Did you mean to ask what war_io_reorder_wmb expand to, or whether there
> are other uses of war_io_reorder_wmb, or what?

 Umm, my question was ill-formed, sorry.  There's a convoluted history 
recorded for that macro in the repo and it could be that it can be removed 
now that we have proper barriers in place, except possibly to avoid the 
Octeon Errata Core-301 (whatever that is).

 Anyway I meant: does `war_io_reorder_wmb' expand to `wmb' on your system?


Powered by blists - more mailing lists