From: David Daney <david.s.daney@gmail.com>
To: Deng-Cheng Zhu <dengcheng.zhu@gmail.com>, ralf@linux-mips.org
Cc: linux-mips@linux-mips.org, a.p.zijlstra@chello.nl,
paulus@samba.org, mingo@elte.hu, acme@redhat.com,
jamie.iles@picochip.com
Subject: Re: [PATCH v6 2/7] MIPS: use generic atomic64 in non-64bit kernels
Date: Wed, 09 Jun 2010 09:58:54 -0700 [thread overview]
Message-ID: <4C0FC84E.8080101@gmail.com> (raw)
In-Reply-To: <1276058130-25851-3-git-send-email-dengcheng.zhu@gmail.com>
On 06/08/2010 09:35 PM, Deng-Cheng Zhu wrote:
> 64bit kernel has already had its atomic64 functions. Except for that, we
> use the generic spinlocked version. The atomic64 types and related
> functions are needed for the Linux performance counter subsystem.
>
> Signed-off-by: Deng-Cheng Zhu<dengcheng.zhu@gmail.com>
I already acked this once, so you can (should) add my...
Acked-by: David Daney <ddaney@caviumnetworks.com>
Really, this part is correct and standalone, so I think Ralf should just
go ahead and merge it to his queue.
David Daney.
> ---
> 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 cdaae94..564e30b 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
> @@ -11,6 +11,7 @@ config MIPS
> select HAVE_FTRACE_MCOUNT_RECORD
> select HAVE_FUNCTION_GRAPH_TRACER
> select RTC_LIB if !MACH_LOONGSON
> + select GENERIC_ATOMIC64 if !64BIT
>
> mainmenu "Linux/MIPS Kernel Configuration"
>
> diff --git a/arch/mips/include/asm/atomic.h b/arch/mips/include/asm/atomic.h
> index 59dc0c7..485ec36 100644
> --- a/arch/mips/include/asm/atomic.h
> +++ b/arch/mips/include/asm/atomic.h
> @@ -782,6 +782,10 @@ static __inline__ int atomic64_add_unless(atomic64_t *v, long a, long u)
> */
> #define atomic64_add_negative(i, v) (atomic64_add_return(i, (v))< 0)
>
> +#else /* !CONFIG_64BIT */
> +
> +#include<asm-generic/atomic64.h>
> +
> #endif /* CONFIG_64BIT */
>
> /*
next prev parent reply other threads:[~2010-06-09 16:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 4:35 [PATCH v6 0/7] MIPS performance event support v6 Deng-Cheng Zhu
2010-06-09 4:35 ` [PATCH v6 1/7] MIPS/Oprofile: extract PMU defines/helper functions for sharing Deng-Cheng Zhu
2010-06-09 4:35 ` [PATCH v6 2/7] MIPS: use generic atomic64 in non-64bit kernels Deng-Cheng Zhu
2010-06-09 16:58 ` David Daney [this message]
2010-08-06 16:45 ` Ralf Baechle
2010-06-09 4:35 ` [PATCH v6 3/7] MIPS: add support for software performance events Deng-Cheng Zhu
2010-09-22 11:38 ` Matt Fleming
2010-06-09 4:35 ` [PATCH v6 4/7] MIPS: add support for hardware performance events (skeleton) Deng-Cheng Zhu
2010-09-22 12:27 ` Matt Fleming
2010-09-23 7:39 ` Deng-Cheng Zhu
2010-09-24 8:36 ` Matt Fleming
2010-09-25 2:53 ` Deng-Cheng Zhu
2010-06-09 4:35 ` [PATCH v6 5/7] MIPS/Perf-events: add callchain support Deng-Cheng Zhu
2010-06-09 4:35 ` [PATCH v6 6/7] MIPS: add support for hardware performance events (mipsxx) Deng-Cheng Zhu
2010-06-09 4:35 ` [PATCH v6 7/7] MIPS: define local_xchg from xchg_local to atomic_long_xchg Deng-Cheng Zhu
2010-09-22 12:32 ` Matt Fleming
2010-09-23 7:56 ` Deng-Cheng Zhu
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=4C0FC84E.8080101@gmail.com \
--to=david.s.daney@gmail.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