[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.21.1903082347330.31648@eddie.linux-mips.org>
Date: Fri, 8 Mar 2019 23:56:03 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Alexandre Oliva <lxoliva@...la.org>
cc: Aaro Koskinen <aaro.koskinen@....fi>, Tom Li <tomli@...li.me>,
James Hogan <jhogan@...nel.org>,
Jiaxun Yang <jiaxun.yang@...goat.com>,
Huacai Chen <chenhc@...ote.com>,
Ralf Baechle <ralf@...ux-mips.org>, linux-mips@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC] On the Current Troubles of Mainlining Loongson Platform
Drivers
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?
Maciej
Powered by blists - more mailing lists