From: "H. Peter Anvin" <hpa@zytor.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Luca Barbieri <luca@luca-barbieri.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-arch@vger.kernel.org
Subject: Re: [GIT PULL] x86/atomic changes for v2.6.35
Date: Wed, 19 May 2010 07:24:00 -0700 [thread overview]
Message-ID: <4BF3F480.3000902@zytor.com> (raw)
In-Reply-To: <AANLkTinWbueCQZdQgZFDLQPJYieB13orxDGYJzzRpPni@mail.gmail.com>
On 05/19/2010 04:46 AM, Geert Uytterhoeven wrote:
> On Tue, May 18, 2010 at 00:45, Ingo Molnar <mingo@elte.hu> wrote:
>> Please pull the latest x86-atomic-for-linus git tree from:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git x86-atomic-for-linus
>>
>>
>> out-of-topic modifications in x86-atomic-for-linus:
>> ---------------------------------------------------
>> lib/Makefile # 86a8938: lib: Add self-test for atomic64_t
>> lib/atomic64.c # 9757789: lib: Fix atomic64_add_unless retu
>> lib/atomic64_test.c # a5c9161: x86, atomic64: In selftest, disti
>> # 25a304f: lib: Fix atomic64_inc_not_zero te
>> # 9efbcd5: lib: Fix atomic64_add_unless test
>> # d7f6de1: x86: Implement atomic[64]_dec_if_
>> # 8f4f202: lib: Only test atomic64_dec_if_po
>> # 86a8938: lib: Add self-test for atomic64_t
>
> Is having atomic64_t mandatory now?
>
> According to the allmodconfig build logs
> (http://kisskb.ellerman.id.au/kisskb/matrix/),
> several architectures (at least m68k and mips) don't have it.
> Furthermore, the test fails to compile on a few architectures that do have it
> (parisc, s390, sh, ...).
>
> <boilerplate>
> It's a pity this wasn't raised/resolved between its detection in linux-next and
> before it entered mainline...
> </boilerplate>
>
Is having atomic64_t mandatory? Not yet, I don't think, but it probably
will be soon -- which is why there is a generic implementation
available. All those architectures just need to select
CONFIG_GENERIC_ATOMIC64 and voilà, problem solved.
As far as your boilerplate is concerned, I think Linus made it clear at
the Kernel Summit that is it not the obligation of x86/ARM/PowerPC to
slow down to not break the smaller architectures; it's the
responsibility of those architecture maintainers to keep up. Sorry.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2010-05-19 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100517224531.GA27400@elte.hu>
2010-05-19 11:46 ` [GIT PULL] x86/atomic changes for v2.6.35 Geert Uytterhoeven
2010-05-19 14:24 ` H. Peter Anvin [this message]
2010-05-19 14:36 ` Stephen Rothwell
2010-05-19 15:01 ` H. Peter Anvin
2010-05-19 15:21 ` Stephen Rothwell
2010-05-19 16:18 ` Paul Mundt
2010-05-19 19:00 ` H. Peter Anvin
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=4BF3F480.3000902@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@luca-barbieri.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).