From: Andrew Morton <akpm@linux-foundation.org>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [bisected] kernel panic 2.6.22 -> 2.6.26-rc9+
Date: Sun, 13 Jul 2008 14:55:25 -0700 [thread overview]
Message-ID: <20080713145525.51a1ca3a.akpm@linux-foundation.org> (raw)
In-Reply-To: <m3lk05jvw5.fsf@maximus.localdomain>
On Sun, 13 Jul 2008 23:51:06 +0200 Krzysztof Halasa <khc@pm.waw.pl> wrote:
> Andrew Morton <akpm@linux-foundation.org> writes:
>
> > --- a/include/asm-arm/bitops.h~a
> > +++ a/include/asm-arm/bitops.h
> > @@ -277,9 +277,16 @@ static inline int constant_fls(int x)
> > * the clz instruction for much better code efficiency.
> > */
> >
> > -#define fls(x) \
> > +#define __fls(x) \
> > ( __builtin_constant_p(x) ? constant_fls(x) : \
> > ({ int __r; asm("clz\t%0, %1" : "=r"(__r) : "r"(x) : "cc"); 32-__r; }) )
> > +
> > +/* Implement fls() in C so that 64-bit args are suitably truncated */
> > +static inline int fls(int x)
> > +{
> > + return __fls(x);
> > +}
> > +
>
> Well, I like it more as it fixes all possible places instead of only
> fls64().
>
> But... can't we just move the #define body into the inline fls(x)?
> Will there be other users of __fls(x)? It seems the
> __builtin_constant_p(x) works for inline functions.
Could. That was a minimal&safe thing.
> The above patch fixes the kernel panic, too.
OK, thanks.
next prev parent reply other threads:[~2008-07-13 21:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 0:28 [bisected] kernel panic 2.6.22 -> 2.6.26-rc9+ Krzysztof Halasa
2008-07-13 8:31 ` Andrew Morton
2008-07-13 10:48 ` Krzysztof Halasa
2008-07-13 18:22 ` Andrew Morton
2008-07-13 21:51 ` Krzysztof Halasa
2008-07-13 21:55 ` Andrew Morton [this message]
2008-07-23 4:52 ` Willy Tarreau
2008-07-23 5:00 ` Andrew Morton
2008-07-23 5:06 ` Willy Tarreau
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=20080713145525.51a1ca3a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=shemminger@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).