linux-kernel - Re: [PATCH -tip] x86: atomic64: inline atomic64

lists.openwall.net		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 linux-hardening linux-cve-announce 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]

Message-ID: <20090703113002.6c2c103b@infradead.org>
Date:	Fri, 3 Jul 2009 11:30:02 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Eric Dumazet <eric.dumazet@...il.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	mingo@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -tip] x86: atomic64: inline atomic64_read()

On Fri, 3 Jul 2009 20:18:15 +0200
Ingo Molnar <mingo@...e.hu> wrote:

> 
> * Arjan van de Ven <arjan@...radead.org> wrote:
> 
> > On Fri, 3 Jul 2009 20:04:50 +0200
> > Ingo Molnar <mingo@...e.hu> wrote:
> > 
> > > > +static inline u64 atomic64_read(atomic64_t *ptr)
> > > > +{
> > > > +	u64 res;
> > > > +
> > > > +	asm volatile(
> > > > +		"mov %%ebx, %%eax\n\t"
> > > > +		"mov %%ecx, %%edx\n\t"
> > > > +		LOCK_PREFIX "cmpxchg8b %1\n"
> > 
> > also afaik cmpxchg implies the lock prefix, so no need to make an
> > explicit one... it just adds code size and alternatives-work
> 
> good point!
> 
> Is the same true of XADD as well? If yes then we can remove the lock 
> prefix from those as well - there's a few uses of that on 32-bit and 
> 64-bit as well.
> 

ok never mind I was wrong,
it seems cmpxchg does NOT imply a lock prefix, nor does xadd.

> 	Ingo


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/