From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86: spinlock ops are always-inlined
Date: Fri, 18 Apr 2008 14:31:10 -0700 [thread overview]
Message-ID: <20080418143110.c8e596c8.akpm@linux-foundation.org> (raw)
In-Reply-To: <200804181847.m3IIlLPr032254@hera.kernel.org>
On Fri, 18 Apr 2008 18:47:21 GMT
Linux Kernel Mailing List <linux-kernel@vger.kernel.org> wrote:
> Gitweb: http://git.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7fda20f146d5d217684ffbc37c6b6c5f82c2dffd
> Commit: 7fda20f146d5d217684ffbc37c6b6c5f82c2dffd
> Parent: d93c870bad38e8daaaf9f7e900a13431f24becbb
> Author: Ingo Molnar <mingo@elte.hu>
> AuthorDate: Fri Feb 29 10:29:38 2008 +0100
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Thu Apr 17 17:41:29 2008 +0200
>
> x86: spinlock ops are always-inlined
>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> ---
> include/asm-x86/spinlock.h | 12 ++++++------
> 1 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/include/asm-x86/spinlock.h b/include/asm-x86/spinlock.h
> index 47dfe26..bc6376f 100644
> --- a/include/asm-x86/spinlock.h
> +++ b/include/asm-x86/spinlock.h
> @@ -78,7 +78,7 @@ static inline int __raw_spin_is_contended(raw_spinlock_t *lock)
> return (((tmp >> 8) & 0xff) - (tmp & 0xff)) > 1;
> }
>
> -static inline void __raw_spin_lock(raw_spinlock_t *lock)
> +static __always_inline void __raw_spin_lock(raw_spinlock_t *lock)
What was the reason for making this change?
next parent reply other threads:[~2008-04-18 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200804181847.m3IIlLPr032254@hera.kernel.org>
2008-04-18 21:31 ` Andrew Morton [this message]
2008-04-21 14:22 ` Ingo Molnar
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=20080418143110.c8e596c8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome