LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu> To: Alexander van Heukelum <heukelum@mailshack.com> Cc: 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] x86: Optimize find_next_(zero_)bit for small constant-size bitmaps Date: Tue, 11 Mar 2008 16:23:03 +0100 [thread overview] Message-ID: <20080311152303.GA21530@elte.hu> (raw) In-Reply-To: <20080311151719.GA15313@mailshack.com> * Alexander van Heukelum <heukelum@mailshack.com> wrote: > > > +#endif /* CONFIG_GENERIC_FIND_NEXT_BIT */ > > > > there should be an #else here i think, which maps find_next_bit to > > __find_next_bit / etc. > > No, that is intentional: architectures are expected to either set > CONFIG_GENERIC_FIND_NEXT_BIT, or provide their own implementation of > find_next_bit. indeed, you are right. > This version runs fine on qemu. great - i've queued it up into x86.git. Ingo
next prev parent reply other threads:[~2008-03-11 15:23 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-09 20:01 [PATCH] x86: Change x86 to use generic find_next_bit Alexander van Heukelum 2008-03-09 20:10 ` Ingo Molnar 2008-03-09 21:03 ` Andi Kleen 2008-03-09 21:32 ` Andi Kleen 2008-03-09 21:13 ` Alexander van Heukelum 2008-03-10 6:29 ` Ingo Molnar 2008-03-09 20:11 ` Ingo Molnar 2008-03-09 20:31 ` Alexander van Heukelum 2008-03-09 20:51 ` Ingo Molnar 2008-03-09 21:29 ` Andi Kleen 2008-03-10 23:17 ` [RFC/PATCH] x86: Optimize find_next_(zero_)bit for small constant-size bitmaps Alexander van Heukelum 2008-03-11 9:56 ` Ingo Molnar 2008-03-11 15:17 ` [PATCH] " Alexander van Heukelum 2008-03-11 15:22 ` [RFC] non-x86: " Alexander van Heukelum 2008-03-11 15:23 ` Ingo Molnar [this message] 2008-03-09 20:28 ` [PATCH] x86: Change x86 to use generic find_next_bit Andi Kleen 2008-03-09 21:31 ` Andi Kleen 2008-03-13 12:44 ` Aneesh Kumar K.V 2008-03-13 14:27 ` Alexander van Heukelum
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=20080311152303.GA21530@elte.hu \ --to=mingo@elte.hu \ --cc=andi@firstfloor.org \ --cc=heukelum@fastmail.fm \ --cc=heukelum@mailshack.com \ --cc=hpa@zytor.com \ --cc=linux-kernel@vger.kernel.org \ --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: linkBe 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).