From: Alex Williamson <alex.williamson@hp.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ia64 <linux-ia64@vger.kernel.org>
Subject: [PATCH] trivial ia64 numa/discontig fixes
Date: Wed, 22 Oct 2003 15:46:21 -0600 [thread overview]
Message-ID: <1066859181.1191.96.camel@patsy.fc.hp.com> (raw)
I stumbled on a couple trivial bugs in ia64 numa/discontig support.
The first just sets the default number of nodes to something reasonable
for a generic kernel, otherwise it's really easy to start walking over
your initdata (more error checking should probably be added). The
second fixes a memcpy to a physical address. Patch below, please
apply. Thanks,
Alex
--
Alex Williamson HP Linux & Open Source Lab
--- linux-2.5/include/asm-ia64/numnodes.h Wed Oct 22 15:14:03 2003
+++ linux-2.5/include/asm-ia64/numnodes.h Wed Oct 22 13:26:08 2003
@@ -4,7 +4,7 @@
#ifdef CONFIG_IA64_DIG
/* Max 8 Nodes */
#define NODES_SHIFT 3
-#elif defined(CONFIG_IA64_SGI_SN2)
+#elif defined(CONFIG_IA64_SGI_SN2) || defined(CONFIG_IA64_GENERIC)
/* Max 128 Nodes */
#define NODES_SHIFT 7
#endif
--- linux-2.5/arch/ia64/mm/discontig.c Wed Oct 22 15:13:48 2003
+++ linux-2.5/arch/ia64/mm/discontig.c Wed Oct 22 15:16:42 2003
@@ -186,7 +186,7 @@
*/
for (cpu = 0; cpu < NR_CPUS; cpu++) {
if (node == node_cpuid[cpu].nid) {
- memcpy(cpu_data, __phys_per_cpu_start,
+ memcpy(__va(cpu_data), __phys_per_cpu_start,
__per_cpu_end-__per_cpu_start);
__per_cpu_offset[cpu] =
(char*)__va(cpu_data) -
next reply other threads:[~2003-10-22 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 21:46 Alex Williamson [this message]
2003-10-22 21:58 ` [PATCH] trivial ia64 numa/discontig fixes Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2003-10-22 21:46 Alex Williamson
2003-10-22 21:58 ` Jesse Barnes
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=1066859181.1191.96.camel@patsy.fc.hp.com \
--to=alex.williamson@hp.com \
--cc=linux-ia64@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.