From: Hugh Dickins <hugh@veritas.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: [PATCH] x86: fix booting non-NUMA system with NUMA config
Date: Fri, 11 Mar 2005 21:19:16 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0503112115180.9801@goblin.wat.veritas.com> (raw)
In-Reply-To: <1110573471.557.73.camel@localhost>
On Fri, 11 Mar 2005, Dave Hansen wrote:
>
> Hugh, you caught me. There is, indeed, a bug booting with
> CONFIG_NUMA=y, CONFIG_X86_GENERICARCH=y, and booting on a non-NUMA
> system. While not the most common configuration, it should surely be
> supported.
Lovely, Dave, thanks a lot, I confirm your patch works for me.
Now I can impress the neighbours again with my little "NUMA" system.
Hugh
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
prev parent reply other threads:[~2005-03-11 21:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.61.0503111922520.9403@goblin.wat.veritas.com>
2005-03-11 20:37 ` Dave Hansen
2005-03-11 21:19 ` Hugh Dickins [this message]
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=Pine.LNX.4.61.0503112115180.9801@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-mm@kvack.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