From: Andrew Morton <akpm@osdl.org>
To: Ashok Raj <ashok.raj@intel.com>
Cc: ashok.raj@intel.com, davidm@hpl.hp.com,
linux-kernel@vger.kernel.org, anil.s.keshavamurthy@intel.com,
pj@sgi.com
Subject: Re: (resend-2) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [6/7]
Date: Wed, 5 May 2004 23:13:50 -0700 [thread overview]
Message-ID: <20040505231350.1d8a3ea6.akpm@osdl.org> (raw)
In-Reply-To: <20040505104739.A24549@unix-os.sc.intel.com>
Ashok Raj <ashok.raj@intel.com> wrote:
>
> Name: cpu_present_map.patch
Ho-hum. Please at least compile-test non-trivial patches with
CONFIG_SMP=n, especially when they dink with bitmasks, bitmaps and
SMP-specific features.
init/main.c: In function `fixup_cpu_present_map':
init/main.c:636: warning: use of compound expressions as lvalues is deprecated
init/main.c:636: error: invalid lvalue in assignment
Due to:
cpu_set(i, cpu_present_map);
It appears that cpu_set() is simply broken on UP:
#define cpu_present_map cpumask_of_cpu(0)
#define cpumask_of_cpu(cpu) ({ ((cpumask_t)1) << (cpu); })
#define cpu_set(cpu, map) do { (void)(cpu); cpus_coerce(map) = 1UL; } while (0)
Put those things together and there's no way it can work. It's not even
conceptually right: cpu_present_map is a "constant" on UP and we have no
business trying to modify it. So perhaps a build error is the appropriate
response.
I'll stick a CONFIG_SMP in the caller, let the bitmap beavers worry about
the more general details.
next prev parent reply other threads:[~2004-05-06 6:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 4:17 (resend) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [6/7] Ashok Raj
2004-05-05 5:59 ` Andrew Morton
2004-05-05 7:03 ` various cpu patches [was: (resend) take3: Updated CPU Hotplug patches] Paul Jackson
2004-05-05 7:14 ` Andrew Morton
2004-05-05 7:28 ` Paul Jackson
2004-05-05 7:24 ` William Lee Irwin III
2004-05-05 7:44 ` Paul Jackson
2004-05-05 7:52 ` William Lee Irwin III
2004-05-05 7:44 ` (resend) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [6/7] Nick Piggin
2004-05-05 14:07 ` Ashok Raj
2004-05-05 17:47 ` (resend-2) " Ashok Raj
2004-05-06 6:13 ` Andrew Morton [this message]
2004-05-06 9:32 ` (resend-3) " Ashok Raj
2004-05-06 9:45 ` Andrew Morton
2004-05-06 9:54 ` Ashok Raj
2004-05-05 17:50 ` (resend-2) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [7/7] Ashok Raj
2004-05-11 23:16 ` (resend) take3: Updated CPU Hotplug patches for IA64 (pj blessed) Patch [6/7] Paul Jackson
2004-05-11 23:38 ` Andrew Morton
2004-05-11 23:55 ` Paul Jackson
2004-05-11 23:58 ` Ashok Raj
2004-05-12 0:37 ` Andrew Morton
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=20040505231350.1d8a3ea6.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=anil.s.keshavamurthy@intel.com \
--cc=ashok.raj@intel.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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