public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Ingo Molnar <mingo@redhat.com>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	Christoph Hellwig <hch@infradead.org>,
	paulus@samba.org, "Martin J. Bligh" <mbligh@mbligh.org>,
	linuxppc-dev@ozlabs.org, Douglas Niehaus <niehaus@eecs.ku.edu>,
	ltt-dev@shafik.org, systemtap@sources.redhat.com,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH 7/9] atomic.h : powerpc
Date: Thu, 21 Dec 2006 14:15:05 +1100	[thread overview]
Message-ID: <1166670905.6673.33.camel@localhost.localdomain> (raw)
In-Reply-To: <20061221001204.GM28643@Krystal>


> +
> +/**
> + * atomic64_add_unless - add unless the number is a given value
> + * @v: pointer of type atomic64_t
> + * @a: the amount to add to v...
> + * @u: ...unless v is equal to u.
> + *
> + * Atomically adds @a to @v, so long as it was not @u.
> + * Returns non-zero if @v was not @u, and zero otherwise.
> + */
> +static __inline__ int atomic64_add_unless(atomic64_t *v, long a, long u)
> +{
> +	long t;
> +
> +	__asm__ __volatile__ (
> +	LWSYNC_ON_SMP
> +"1:	ldarx	%0,0,%1		# atomic_add_unless\n\
> +	cmpd	0,%0,%3 \n\
> +	beq-	2f \n\
> +	add	%0,%2,%0 \n"
> +	PPC405_ERR77(0,%2)
> +"	stdcx.	%0,0,%1 \n\
> +	bne-	1b \n"
> +	ISYNC_ON_SMP
> +"	subf	%0,%2,%0 \n\
> +2:"
> +	: "=&r" (t)
> +	: "r" (&v->counter), "r" (a), "r" (u)
> +	: "cc", "memory");
> +
> +	return t != u;
> +}
> +

You shouldn't try to define those when building 32 bits code... Also,
the PPC405 errata, as it's name implies, is specific to 405 cores which
are all 32 bits.

Ben.



  reply	other threads:[~2006-12-21  3:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21  0:03 [PATCH 0/9] atomic.h : standardising atomic primitives Mathieu Desnoyers
2006-12-21  0:06 ` [PATCH 1/9] atomic.h : alpha architecture Mathieu Desnoyers
2006-12-21  0:07 ` [PATCH 2/9] atomic.h : generic atomic_long Mathieu Desnoyers
2006-12-21  0:08 ` [PATCH 3/9] atomic.h : i386 "64 bits" ready fix Mathieu Desnoyers
2006-12-21  0:09 ` [PATCH 4/9] atomic.h : ia64 Mathieu Desnoyers
2006-12-21  0:10 ` [PATCH 5/9] atomic.h : standardising atomic primitives Mathieu Desnoyers
2006-12-21  0:10 ` [PATCH 6/9] atomic.h : parisc Mathieu Desnoyers
2006-12-21  0:12 ` [PATCH 7/9] atomic.h : powerpc Mathieu Desnoyers
2006-12-21  3:15   ` Benjamin Herrenschmidt [this message]
2006-12-21  3:29     ` Mathieu Desnoyers
2006-12-21  0:12 ` [PATCH 8/9] atomic.h : sparc Mathieu Desnoyers
2006-12-21  0:14 ` [PATCH 9/9] atomic.h : x86_64 Mathieu Desnoyers
2006-12-21 19:42   ` [PATCH] atomic.h : x86_64 atomic64_add_return Mathieu Desnoyers

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1166670905.6673.33.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=ltt-dev@shafik.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mbligh@mbligh.org \
    --cc=mingo@redhat.com \
    --cc=niehaus@eecs.ku.edu \
    --cc=paulus@samba.org \
    --cc=systemtap@sources.redhat.com \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox