From: Andrew Morton <akpm@osdl.org>
To: Daniel Walker <dwalker@mvista.com>
Cc: linux-kernel@vger.kernel.org, dwalker@mvista.com, hzhong@gmail.com
Subject: Re: [PATCH] Profile likely/unlikely macros -v2
Date: Wed, 26 Apr 2006 21:48:08 -0700 [thread overview]
Message-ID: <20060426214808.6c478edc.akpm@osdl.org> (raw)
In-Reply-To: <200604262145.k3QLjixA005676@dwalker1.mvista.com>
Daniel Walker <dwalker@mvista.com> wrote:
>
> Changes are switched to test_and_set_bit()/clear_bit() ,
> comment explaining test_and_set_bit(), and most every
> other comment ..
I too am getting undefined you_cannot_kmalloc_that_much on x86_64. Coming
out of
cache_kobject[cpu] = kmalloc(sizeof(struct kobject), GFP_KERNEL);
in arch/i386/kernel/cpu/intel_cacheinfo.c
It has to be a compiler bug, I think.
gcc (GCC) 3.4.2 20041017 (Red Hat 3.4.2-6.fc3)
I cannot use this patch until we find a workaround.
next prev parent reply other threads:[~2006-04-27 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 21:45 [PATCH] Profile likely/unlikely macros -v2 Daniel Walker
2006-04-26 21:47 ` Hua Zhong
2006-04-27 4:48 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-27 4:58 Hua Zhong
2006-04-27 6:10 ` Hua Zhong
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=20060426214808.6c478edc.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=dwalker@mvista.com \
--cc=hzhong@gmail.com \
--cc=linux-kernel@vger.kernel.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