[PATCH 2/6] arm64: barriers: make use of barrier options with explicit barriers
Will Deacon
will.deacon at arm.com
Thu Feb 6 06:45:59 EST 2014
On Thu, Feb 06, 2014 at 11:41:30AM +0000, Catalin Marinas wrote:
> On Thu, Feb 06, 2014 at 11:30:49AM +0000, Will Deacon wrote:
> > --- a/arch/arm64/include/asm/barrier.h
> > +++ b/arch/arm64/include/asm/barrier.h
> > @@ -20,14 +20,14 @@
> >
> > #ifndef __ASSEMBLY__
> >
> > -#define sev() asm volatile("sev" : : : "memory")
> > +#define sev(l) asm volatile("sev" #l : : : "memory")
>
> Would we actually ever use sev(l) form C? And it's a new instruction
> rather than an argument to the existing sev.
I don't know, but if it's not there then I'm pretty sure people will always
use sev, even if sevl could be used. In fact, sev and sevl are both aliases
of hint, so they're the same instruction with different immediate operands.
Will
More information about the linux-arm-kernel
mailing list