[<prev] [next>] [day] [month] [year] [list]
Message-ID: <521EA99B.3010303@cn.fujitsu.com>
Date: Thu, 29 Aug 2013 09:53:31 +0800
From: Tang Chen <tangchen@...fujitsu.com>
To: Wanpeng Li <liwanp@...ux.vnet.ibm.com>
CC: Tejun Heo <tj@...nel.org>, rjw@...k.pl, lenb@...nel.org,
tglx@...utronix.de, mingo@...e.hu, hpa@...or.com,
akpm@...ux-foundation.org, trenn@...e.de, yinghai@...nel.org,
jiang.liu@...wei.com, wency@...fujitsu.com, laijs@...fujitsu.com,
isimatu.yasuaki@...fujitsu.com, izumi.taku@...fujitsu.com,
mgorman@...e.de, minchan@...nel.org, mina86@...a86.com,
gong.chen@...ux.intel.com, vasilis.liaskovitis@...fitbricks.com,
lwoodman@...hat.com, riel@...hat.com, jweiner@...hat.com,
prarit@...hat.com, zhangyanfei@...fujitsu.com, x86@...nel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-acpi@...r.kernel.org
Subject: Re: [PATCH 00/11] x86, memblock: Allocate memory near kernel image
before SRAT parsed.
Hi Wanpeng,
On 08/29/2013 09:36 AM, Wanpeng Li wrote:
......
>> Hi tj,
>>
>> Sorry for the trouble. Please refer to the following branch:
>>
>> https://github.com/imtangchen/linux.git movablenode-boot-option
>>
>
> Could you post your testcase? So I can test it on x86 and powerpc machines.
>
Sure. Some simple testcases:
1. Boot the kernel without movablenode boot option, check if the memory
mapping
is initialized as before, high to low.
2. Boot the kernel with movablenode boot option, check if the memory
mapping
is initialized as before, low to high.
3. With movablenode, check if the memory allocation is from high to low
after
SRAT is parsed.
4. Check if we can do acpi_initrd_override normally with and without
movablenode.
And the memory allocation is from low to high, near the end of
kernel image.
5. with movablenode, check if crashkernel boot option works normally.
(This may consume a lot of memory, but should work normally.)
6. With movablenode, check if relocate_initrd() works normally.
(This may consume a lot of memory, but should work normally.)
7. With movablenode, check if kexec could locate the kernel to higher
memory.
(This may consume hotplug memory if higher memory is hotpluggable,
but should work normally.)
Please do the above tests with and without the following config options:
1. CONFIG_MOVABLE_NODE
2. CONFIG_ACPI_INITRD_OVERRIDE
Thanks for the testing.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists