From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: kosaki.motohiro@jp.fujitsu.com, mingo@elte.hu,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
apw@shadowen.org
Subject: Re: [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86
Date: Wed, 23 Jan 2008 11:04:13 +0900 [thread overview]
Message-ID: <20080123105810.F295.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <20080121093702.8FC2.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Hi mel
> Hi
>
> > A fix[1] was merged to the x86.git tree that allowed NUMA kernels to boot
> > on normal x86 machines (and not just NUMA-Q, Summit etc.). I took a look
> > at the restrictions on setting NUMA on x86 to see if they could be lifted.
>
> Interesting!
>
> I will test tomorrow.
Hmm...
It doesn't works on my machine.
panic at booting at __free_pages_ok() with blow call trace.
[<hex number>] free_all_bootmem_core
[<hex number>] mem_init
[<hex number>] alloc_large_system_hash
[<hex number>] inode_init_early
[<hex number>] start_kernel
[<hex number>] unknown_bootoption
my machine spec
CPU: Pentium4 with HT
MEM: 512M
I will try more investigate.
but I have no time for a while, sorry ;-)
BTW:
when config sparse mem turn on instead discontig mem.
panic at booting at get_pageblock_flags_group() with below call stack.
free_initrd
free_init_pages
free_hot_cold_page
- kosaki
next prev parent reply other threads:[~2008-01-23 2:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 15:35 [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 Mel Gorman
2008-01-18 15:35 ` [PATCH 1/2] Do not require CONFIG_HIGHMEM64G to set " Mel Gorman
2008-01-18 16:17 ` Ingo Molnar
2008-01-18 15:36 ` [PATCH 2/2] Allow any x86 sub-architecture type to set CONFIG_NUMA Mel Gorman
2008-01-18 16:17 ` Ingo Molnar
2008-01-19 6:35 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 Andi Kleen
2008-01-19 16:07 ` Mel Gorman
2008-01-22 12:14 ` Ingo Molnar
2008-01-22 12:29 ` Mel Gorman
2008-01-22 15:39 ` Ingo Molnar
2008-01-22 13:33 ` Andi Kleen
2008-01-23 10:28 ` Mel Gorman
2008-01-23 10:45 ` Andi Kleen
2008-01-23 10:57 ` Mel Gorman
2008-01-23 11:11 ` Andi Kleen
2008-01-23 11:15 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 II Andi Kleen
2008-01-23 11:24 ` Mel Gorman
2008-01-23 13:48 ` Andi Kleen
2008-01-23 14:15 ` Mel Gorman
2008-01-21 0:38 ` [PATCH 0/2] Relax restrictions on setting CONFIG_NUMA on x86 KOSAKI Motohiro
2008-01-21 14:35 ` Mel Gorman
2008-01-21 14:49 ` Ingo Molnar
2008-01-21 16:27 ` Mel Gorman
2008-01-23 2:04 ` KOSAKI Motohiro [this message]
2008-01-23 10:22 ` Mel Gorman
2008-01-24 3:19 ` KOSAKI Motohiro
2008-01-23 10:23 ` Mel Gorman
2008-01-26 14:10 ` KOSAKI Motohiro
2008-01-26 17:10 ` KOSAKI Motohiro
2008-01-26 17:18 ` Mel Gorman
2008-01-27 6:54 ` KOSAKI Motohiro
2008-01-28 15:02 ` Ingo Molnar
2008-01-29 2:57 ` KOSAKI Motohiro
2008-01-29 11:34 ` Mel Gorman
2008-02-03 9:32 ` KOSAKI Motohiro
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=20080123105810.F295.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
/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;
as well as URLs for NNTP newsgroup(s).