[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- To: Leonid Yegoshin <Leonid.Yegoshin@xxxxxxxxxx>
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Date: Thu, 14 Jan 2016 21:15:13 +0100
- Cc: linux-mips@xxxxxxxxxxxxxx, linux-ia64@xxxxxxxxxxxxxxx, "Michael S. Tsirkin" <mst@xxxxxxxxxx>, Will Deacon <will.deacon@xxxxxxx>, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxx>, sparclinux@xxxxxxxxxxxxxxx, Ingo Molnar <mingo@xxxxxxxxxx>, linux-arch@xxxxxxxxxxxxxxx, linux-s390@xxxxxxxxxxxxxxx, Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx>, user-mode-linux-devel@xxxxxxxxxxxxxxxxxxxxx, linux-sh@xxxxxxxxxxxxxxx, Michael Ellerman <mpe@xxxxxxxxxxxxxx>, x86@xxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxx, Ingo Molnar <mingo@xxxxxxx>, paulmck@xxxxxxxxxxxxxxxxxx, linux-xtensa@xxxxxxxxxxxxxxxx, james.hogan@xxxxxxxxxx, Arnd Bergmann <arnd@xxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, adi-buildroot-devel@xxxxxxxxxxxxxxxxxxxxx, ddaney.cavm@xxxxxxxxx, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, linux-metag@xxxxxxxxxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Ralf Baechle <ralf@xxxxxxxxxxxxxx>, Joe Perches <joe@xxxxxxxxxxx>, linuxppc-dev@xxxxxxxxxxxxxxxx, David Miller <davem@xxxxxxxxxxxxx>
- Delivery-date: Thu, 14 Jan 2016 20:15:48 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
On Thu, Jan 14, 2016 at 11:42:02AM -0800, Leonid Yegoshin wrote:
> An the only point - please use an appropriate SYNC_* barriers instead of
> heavy bold hammer. That stuff was design explicitly to support the
> requirements of Documentation/memory-barriers.txt
That's madness. That document changes from version to version as to what
we _think_ the actual hardware does. It is _NOT_ a specification.
You cannot design hardware from that. Its incomplete and fails to
specify a bunch of things. It not a mathematically sound definition of a
memory model.
Please stop referring to that document for what a particular barrier
_should_ do. Explain what MIPS does, so we can attempt to integrate
this knowledge with our knowledge of PPC/ARM/Alpha/x86/etc. and improve
upon our understanding of hardware and improve the Linux memory model.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
- References:
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
- Re: [Xen-devel] [v3,11/41] mips: reuse asm-generic/barrier.h
|