From: Randy Dunlap <randy.dunlap@oracle.com>
To: Alexander van Heukelum <heukelum@mailshack.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
Ingo Molnar <mingo@elte.hu>,
Alexander van Heukelum <heukelum@fastmail.fm>,
Andi Kleen <andi@firstfloor.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] x86: merge the simple bitops and move them to bitops.h
Date: Fri, 14 Mar 2008 16:30:37 -0700 [thread overview]
Message-ID: <20080314163037.e15a49db.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080314203526.GA13959@mailshack.com>
On Fri, 14 Mar 2008 21:35:26 +0100 Alexander van Heukelum wrote:
> x86: merge the simple bitops and move them to bitops.h.
>
>
> Improved comments for ffs and fls.
There is still room for some comment improvements IMO. See below.
> Signed-off-by: Alexander van Heukelum <heukelum@fastmail.fm>
>
> ---
>
> diff --git a/include/asm-x86/bitops.h b/include/asm-x86/bitops.h
> index 1a23ce1..363a4ff 100644
> --- a/include/asm-x86/bitops.h
> +++ b/include/asm-x86/bitops.h
> @@ -310,6 +309,104 @@ static int test_bit(int nr, const volatile unsigned long *addr);
> constant_test_bit((nr),(addr)) : \
> variable_test_bit((nr),(addr)))
>
> +/**
> + * __ffs - find first bit in word.
find first bit set in word
[The "first bit in word" could have any value in {0, 1}, so the
return value would depend on which end you considered "first". ;]
> + * @word: The word to search
> + *
> + * Undefined if no bit exists, so code should check against 0 first.
> + */
> +static inline unsigned long __ffs(unsigned long word)
> +{
> + __asm__("bsf %1,%0"
> + :"=r" (word)
> + :"rm" (word));
> + return word;
> +}
> +
> +/**
> + * ffz - find first zero in word.
find first zero bit in word
> + * @word: The word to search
> + *
> + * Undefined if no zero exists, so code should check against ~0UL first.
> + */
> +static inline unsigned long ffz(unsigned long word)
> +{
> + __asm__("bsf %1,%0"
> + :"=r" (word)
> + :"r" (~word));
> + return word;
> +}
> +
> +/*
> + * __fls: find last bit set.
__fls - find last bit set in word
> + * @word: The word to search
> + *
> + * Undefined if no zero exists, so code should check against ~0UL first.
> + */
> +static inline unsigned long __fls(unsigned long word)
> +{
> + __asm__("bsr %1,%0"
> + :"=r" (word)
> + :"rm" (word));
> + return word;
> +}
> +
> +#ifdef __KERNEL__
> +/**
> + * ffs - find first bit set
in word
> + * @x: the word to search
> + *
> + * This is defined the same way as the libc and compiler builtin ffs
> + * routines, therefore differs in spirit from the other bitops.
> + *
> + * ffs(value) returns 0 if value is 0 or the position of the first
> + * set bit if value is nonzero. The first (least significant) bit
> + * is at position 1.
> + */
> +static inline int ffs(int x)
> +{
> + int r;
> +#ifdef CONFIG_X86_CMOV
> + __asm__("bsfl %1,%0\n\t"
> + "cmovzl %2,%0"
> + : "=r" (r) : "rm" (x), "r" (-1));
> +#else
> + __asm__("bsfl %1,%0\n\t"
> + "jnz 1f\n\t"
> + "movl $-1,%0\n"
> + "1:" : "=r" (r) : "rm" (x));
> +#endif
> + return r + 1;
> +}
> +
> +/**
> + * fls - find last bit set
in word
> + * @x: the word to search
> + *
> + * This is defined in a similar way as the libc and compiler builtin
> + * ffs, but returns the position of the most significant set bit.
> + *
> + * fls(value) returns 0 if value is 0 or the position of the last
> + * set bit if value is nonzero. The last (most significant) bit is
> + * at position 32.
> + */
> +static inline int fls(int x)
> +{
> + int r;
> +#ifdef CONFIG_X86_CMOV
> + __asm__("bsrl %1,%0\n\t"
> + "cmovzl %2,%0"
> + : "=&r" (r) : "rm" (x), "rm" (-1));
> +#else
> + __asm__("bsrl %1,%0\n\t"
> + "jnz 1f\n\t"
> + "movl $-1,%0\n"
> + "1:" : "=r" (r) : "rm" (x));
> +#endif
> + return r + 1;
> +}
> +#endif /* __KERNEL__ */
---
~Randy
next prev parent reply other threads:[~2008-03-14 23:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 20:01 [PATCH] " Alexander van Heukelum
2008-03-14 18:07 ` Jeremy Fitzhardinge
2008-03-14 19:43 ` Alexander van Heukelum
2008-03-14 19:55 ` Andi Kleen
2008-03-14 21:33 ` Alexander van Heukelum
2008-03-14 21:42 ` Andi Kleen
2008-03-14 22:01 ` Alexander van Heukelum
2008-03-14 22:18 ` Andi Kleen
2008-03-15 17:54 ` Alexander van Heukelum
2008-03-15 19:19 ` K8, EFFICEON and CORE2 support the cmovxx instructions Alexander van Heukelum
2008-03-15 20:18 ` H. Peter Anvin
2008-03-15 21:06 ` Alexander van Heukelum
2008-03-15 21:11 ` Willy Tarreau
2008-03-16 13:16 ` [PATCH] x86: K8, GEODE_LX, CRUSOE, " Alexander van Heukelum
2008-03-21 12:38 ` Ingo Molnar
2008-03-14 20:35 ` [PATCH v2] x86: merge the simple bitops and move them to bitops.h Alexander van Heukelum
2008-03-14 23:30 ` Randy Dunlap [this message]
2008-03-15 12:04 ` [PATCH v3] " Alexander van Heukelum
2008-03-21 12:35 ` Ingo Molnar
2008-03-14 21:15 ` [PATCH] " Jeremy Fitzhardinge
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=20080314163037.e15a49db.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=andi@firstfloor.org \
--cc=heukelum@fastmail.fm \
--cc=heukelum@mailshack.com \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
Powered by JetHome