Hi,
How about hiding memory completely,which is onlined after boot, at boot-time ?
memmap= option will enable it.
Now, I use this one :)
===
title MemHotPlug (for test)
root (hd0,0)
kernel /vmlinuz-2.6.10-rc1-mm5-mhp1 ro root=/dev/hda5 mem=512m memmap=256m#512m vmalloc=512m
initrd /initrd-2.6.10-rc1-mm5-mhp1.imgkernel
(my machine has only 758MB mems)
===
memmap=256m#512m means "memory range 512m to (512 + 256)m is reserved by acpi"
With this, this area is not used by any functions and devices.
no memory viocaltion will occur which is caused by devices.
And I can run X-window with this :)
This check is helpful when it looks that someone destroies newly-allocated pages.
Thanks
-- Kame
Mark Wong wrote:
> Hi,
>
> I was trying out tests-041126 against the 2.6.10-rc1-mm5-mhp1 with
> page_section, local_memmap, local_memalloc, lru_drain_wq, nonlinear
> and nowriteback patches applied on top of that. I get the following
> oops when I run make test, let me know if I can provide more
> information:
>
> # make test
> ./run.sh 5 ./aioalloc
> online 8 (0x40000000)
>
> Oops: 0000 [#1]
> PREEMPT SMP
> Modules linked in:
> CPU: 1
> EIP: 0060:[<c01669cf>] Not tainted VLI
> EFLAGS: 00010286 (2.6.10-rc1-mm5-mhp4)
> EIP is at online_pages+0x7f/0xb0
> eax: 2073096d ebx: 00000000 ecx: 2073096d edx: 2073096d
> esi: ffcae800 edi: 00008000 ebp: f747f3e0 esp: f750eea0
> ds: 007b es: 007b ss: 0068
> Process sh (pid: 6997, threadinfo=f750e000 task=f7da3020)
> Stack: ffcae800 c0367c2e 00008000 ffcae800 f888a000 00008000 00000008 c0278223
> ffcae800 00008000 00000008 f888a000 f89a9fdc 00000008 00000002 f747f3e0
> 00000001 c038d9ed ffffffea c02782bf f747f3e0 00000001 00000007 f7dab006
> Call Trace:
> [<c0278223>] memory_block_action+0x153/0x1a0
> [<c02782bf>] memory_block_change_state+0x4f/0x60
> [<c02783be>] store_mem_state+0xee/0x140
> [<c02736e5>] sysdev_store+0x35/0x40
> [<c01a205e>] flush_write_buffer+0x3e/0x50
> [<c01a20e4>] sysfs_write_file+0x74/0x90
> [<c016a218>] vfs_write+0xc8/0x170
> [<c016a391>] sys_write+0x51/0x80
> [<c0106423>] syscall_call+0x7/0xb
> Code: 89 44 24 04 c7 04 24 78 b5 37 c0 e8 fc c6 fb ff 83 c4 10 31 c0 5b 5e 5f c3 8d 76 00 8d 04 33 89 04 24 e8 35 f8 ff ff 89 c2 89 c1 <8b> 00 a9 00 80 00 00 74 03 8b 4a 0c 8b 41 04 40 74 07 43 39 fb
> <0>Fatal exception: panic in 5 seconds
> Kernel panic - not syncing: Fatal exception
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://productguide.itmanagersjournal.com/
> _______________________________________________
> Lhms-devel mailing list
> Lhms-devel@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/lhms-devel
>
--
--the clue is these footmarks leading to the door.--
KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
