From: David Daney <ddaney@caviumnetworks.com>
To: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org,
a.p.zijlstra@chello.nl, paulus@samba.org, mingo@elte.hu,
acme@redhat.com, jamie.iles@picochip.com
Subject: Re: [PATCH 1/3] MIPS: use the generic atomic64 operations for perf counter support
Date: Tue, 20 Apr 2010 09:25:51 -0700 [thread overview]
Message-ID: <4BCDD58F.7020201@caviumnetworks.com> (raw)
In-Reply-To: <1271349525.7467.420.camel@fun-lab>
On 04/15/2010 09:38 AM, Deng-Cheng Zhu wrote:
> Currently we take the generic spinlock'ed atomic64 implementation from the
> lib. The atomic64 types and related functions are needed for the Linux
> performance counter subsystem.
>
> Signed-off-by: Deng-Cheng Zhu<dengcheng.zhu@gmail.com>
NAK.
> ---
> arch/mips/Kconfig | 1 +
> arch/mips/include/asm/atomic.h | 4 ++++
> 2 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 29e8692..7161751 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -4,6 +4,7 @@ config MIPS
> select HAVE_GENERIC_DMA_COHERENT
> select HAVE_IDE
> select HAVE_OPROFILE
> + select GENERIC_ATOMIC64
> select HAVE_ARCH_KGDB
> select HAVE_FUNCTION_TRACER
> select HAVE_FUNCTION_TRACE_MCOUNT_TEST
> diff --git a/arch/mips/include/asm/atomic.h b/arch/mips/include/asm/atomic.h
> index 519197e..b0a932e 100644
> --- a/arch/mips/include/asm/atomic.h
> +++ b/arch/mips/include/asm/atomic.h
> @@ -21,6 +21,10 @@
> #include<asm/war.h>
> #include<asm/system.h>
>
> +#ifdef CONFIG_GENERIC_ATOMIC64
> +#include<asm-generic/atomic64.h>
> +#endif
> +
> #define ATOMIC_INIT(i) { (i) }
>
> /*
This is incorrect. For 64-bit kernels, we already have all the 64-bit
atomics implemented. This will break 64-bit kernels.
David Daney
next prev parent reply other threads:[~2010-04-20 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 16:38 [PATCH 1/3] MIPS: use the generic atomic64 operations for perf counter support Deng-Cheng Zhu
2010-04-20 16:25 ` David Daney [this message]
2010-04-21 17:19 ` Ralf Baechle
2010-04-21 17:45 ` David Daney
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=4BCDD58F.7020201@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=dengcheng.zhu@gmail.com \
--cc=jamie.iles@picochip.com \
--cc=linux-mips@linux-mips.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
/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