Mailinglist Archive: radeonhd (312 mails)
| < Previous | Next > |
Re: [radeonhd] [patch] Use MMIO macros for portability
- From: Matthias Hopf <mhopf@xxxxxxx>
- Date: Thu, 2 Apr 2009 15:56:18 +0200
- Message-id: <20090402135618.GC15366@xxxxxxx>
On Mar 26, 09 09:45:46 +1300, Michael Cree wrote:
I just checked the linux kernel headers (mb macro):
It's a NOP on cris, m32r, m68k, mn10300, parisc, and xtensa.
It's actual code on frv, mips, and x86.
I stand corrected, though I'm puzzled which x86 processors need barriers
(the comments in the code states "Some non-Intel clones support out of
order store. wmb() ceases to be a * nop for these."). I don't think
Athlons do that.
BTW - what architecture is frv? How is powerpc, alpha, and ia64 called
in kernel land? Do you happen to know?
CU
Matthias
--
Matthias Hopf <mhopf@xxxxxxx> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@xxxxxxxxx
Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
Memory barriers, at least of some sort, are defined to be non-empty in
compiler.h for the following architectures: alpha, ia64, amd64, mips and
powerpc.
I just checked the linux kernel headers (mb macro):
It's a NOP on cris, m32r, m68k, mn10300, parisc, and xtensa.
It's actual code on frv, mips, and x86.
I stand corrected, though I'm puzzled which x86 processors need barriers
(the comments in the code states "Some non-Intel clones support out of
order store. wmb() ceases to be a * nop for these."). I don't think
Athlons do that.
BTW - what architecture is frv? How is powerpc, alpha, and ia64 called
in kernel land? Do you happen to know?
CU
Matthias
--
Matthias Hopf <mhopf@xxxxxxx> __ __ __
Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@xxxxxxxxx
Phone +49-911-74053-715 __) |_| __) |__ R & D www.mshopf.de
--
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx
| < Previous | Next > |