From: Chris Wright <chrisw@osdl.org>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: Chris Wright <chrisw@osdl.org>,
William Lee Irwin III <wli@holomorphy.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: node_online_map patch kills x86_64
Date: Wed, 12 Jan 2005 11:20:15 -0800 [thread overview]
Message-ID: <20050112112015.P24171@build.pdx.osdl.net> (raw)
In-Reply-To: <1105555323.8266.2.camel@arrakis>; from colpatch@us.ibm.com on Wed, Jan 12, 2005 at 10:42:03AM -0800
* Matthew Dobson (colpatch@us.ibm.com) wrote:
> On Tue, 2005-01-11 at 16:35, Chris Wright wrote:
> > Thanks wli. Seems Andi understands the issue despite my unintelligible
> > bug report ;-)
> >
> > thanks,
> > -chris
>
> So I assume you were trying to saying that backing out the patches makes
> the machine boot, and leaving them in kills it, right?
Yes, exactly. Not sure which part of my brain was misfiring when I
wrote that gibberish ;-)
> And does Andi's
> "[PATCH] x86_64: Optimize nodemask operations slightly" fix your
> problem? I'm assuming that's what the reference to "Andi understanding
> the issue" meant? Or is there still a problem booting x86_64 with the
> numnodes -> node_online_map patches?
The patch from Andi that I tested which fixed the issue for me was:
Index: linux/arch/x86_64/mm/srat.c
===================================================================
--- linux.orig/arch/x86_64/mm/srat.c 2005-01-09 18:19:17.%N +0100
+++ linux/arch/x86_64/mm/srat.c 2005-01-12 02:43:54.%N +0100
@@ -29,8 +29,8 @@
if (pxm2node[pxm] == 0xff) {
if (num_online_nodes() >= MAX_NUMNODES)
return -1;
- pxm2node[pxm] = num_online_nodes();
- node_set_online(num_online_nodes());
+ pxm2node[pxm] = num_online_nodes() - 1;
+ node_set_online(pxm2node[pxm]);
}
return pxm2node[pxm];
}
This looks like just a straight fix for the following from your patch (AFAICT):
- pxm2node[pxm] = numnodes - 1;
- numnodes++;
+ pxm2node[pxm] = num_online_nodes();
+ node_set_online(num_online_nodes());
However, what's in bk is a bit different and it too is working well:
http://linux.bkbits.net:8080/linux-2.6/gnupatch@41e543d4Ujgg-Hk9pyWGiXvs7oXkBw
Hope that clarifies. Thanks.
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
next prev parent reply other threads:[~2005-01-12 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 23:16 node_online_map patch kills x86_64 Chris Wright
2005-01-11 23:42 ` Andi Kleen
2005-01-12 0:30 ` Chris Wright
2005-01-12 1:38 ` Andi Kleen
2005-01-12 1:53 ` Chris Wright
2005-01-12 2:00 ` Andi Kleen
2005-01-12 2:10 ` Chris Wright
2005-01-12 0:07 ` William Lee Irwin III
2005-01-12 0:35 ` Chris Wright
2005-01-12 18:42 ` Matthew Dobson
2005-01-12 19:20 ` Chris Wright [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-12 2:03 Petr Vandrovec
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=20050112112015.P24171@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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