Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-26 Thread Yasuaki Ishimatsu
Hi Tang, 2012/12/26 16:39, Tang Chen wrote: > On 12/26/2012 02:53 PM, Yasuaki Ishimatsu wrote: >> Hi Tang, >> >> I don't think it can work well. >> The patch gets memory range of hotpluggable memory by >> acpi_numa_memory_affinity_init(). But it too late. >> For example, if we use log_buf_len

Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-26 Thread Yasuaki Ishimatsu
Hi Tang, 2012/12/26 16:39, Tang Chen wrote: On 12/26/2012 02:53 PM, Yasuaki Ishimatsu wrote: Hi Tang, I don't think it can work well. The patch gets memory range of hotpluggable memory by acpi_numa_memory_affinity_init(). But it too late. For example, if we use log_buf_len boot options,

Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-25 Thread Tang Chen
On 12/26/2012 02:53 PM, Yasuaki Ishimatsu wrote: > Hi Tang, > > I don't think it can work well. > The patch gets memory range of hotpluggable memory by > acpi_numa_memory_affinity_init(). But it too late. > For example, if we use log_buf_len boot options, memblock allocator > runs before getting

Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-25 Thread Yasuaki Ishimatsu
Hi Tang, I don't think it can work well. The patch gets memory range of hotpluggable memory by acpi_numa_memory_affinity_init(). But it too late. For example, if we use log_buf_len boot options, memblock allocator runs before getting SRAT information. In this case, this movablecore_map boot

Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-25 Thread Yasuaki Ishimatsu
Hi Tang, I don't think it can work well. The patch gets memory range of hotpluggable memory by acpi_numa_memory_affinity_init(). But it too late. For example, if we use log_buf_len boot options, memblock allocator runs before getting SRAT information. In this case, this movablecore_map boot

Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-25 Thread Tang Chen
On 12/26/2012 02:53 PM, Yasuaki Ishimatsu wrote: Hi Tang, I don't think it can work well. The patch gets memory range of hotpluggable memory by acpi_numa_memory_affinity_init(). But it too late. For example, if we use log_buf_len boot options, memblock allocator runs before getting SRAT

Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-19 Thread Tang Chen
On 12/19/2012 04:15 PM, Tang Chen wrote: The Hot Plugable bit in SRAT flags specifys if the memory range could be hotplugged. If user specified movablecore_map=nn[KMG]@ss[KMG], reset movablecore_map.map to the intersection of hotpluggable ranges from SRAT and old movablecore_map.map. Else if

[PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-19 Thread Tang Chen
The Hot Plugable bit in SRAT flags specifys if the memory range could be hotplugged. If user specified movablecore_map=nn[KMG]@ss[KMG], reset movablecore_map.map to the intersection of hotpluggable ranges from SRAT and old movablecore_map.map. Else if user specified movablecore_map=acpi, just use

[PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-19 Thread Tang Chen
The Hot Plugable bit in SRAT flags specifys if the memory range could be hotplugged. If user specified movablecore_map=nn[KMG]@ss[KMG], reset movablecore_map.map to the intersection of hotpluggable ranges from SRAT and old movablecore_map.map. Else if user specified movablecore_map=acpi, just use

[PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-19 Thread Tang Chen
The Hot Plugable bit in SRAT flags specifys if the memory range could be hotplugged. If user specified movablecore_map=nn[KMG]@ss[KMG], reset movablecore_map.map to the intersection of hotpluggable ranges from SRAT and old movablecore_map.map. Else if user specified movablecore_map=acpi, just use

[PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-19 Thread Tang Chen
The Hot Plugable bit in SRAT flags specifys if the memory range could be hotplugged. If user specified movablecore_map=nn[KMG]@ss[KMG], reset movablecore_map.map to the intersection of hotpluggable ranges from SRAT and old movablecore_map.map. Else if user specified movablecore_map=acpi, just use

Re: [PATCH v4 3/6] ACPI: Restructure movablecore_map with memory info from SRAT.

2012-12-19 Thread Tang Chen
On 12/19/2012 04:15 PM, Tang Chen wrote: The Hot Plugable bit in SRAT flags specifys if the memory range could be hotplugged. If user specified movablecore_map=nn[KMG]@ss[KMG], reset movablecore_map.map to the intersection of hotpluggable ranges from SRAT and old movablecore_map.map. Else if