Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Baoquan, At 02/08/2018 09:23 AM, Baoquan He wrote: On 02/08/18 at 09:14am, Dou Liyang wrote: Hi Baoquan, At 02/07/2018 08:45 PM, Baoquan He wrote: On 02/07/18 at 08:34pm, Dou Liyang wrote: At 02/07/2018 08:27 PM, Baoquan He wrote: On 02/07/18 at 08:17pm, Dou Liyang wrote: Hi Baoquan,

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Baoquan, At 02/08/2018 09:23 AM, Baoquan He wrote: On 02/08/18 at 09:14am, Dou Liyang wrote: Hi Baoquan, At 02/07/2018 08:45 PM, Baoquan He wrote: On 02/07/18 at 08:34pm, Dou Liyang wrote: At 02/07/2018 08:27 PM, Baoquan He wrote: On 02/07/18 at 08:17pm, Dou Liyang wrote: Hi Baoquan,

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/08/18 at 09:14am, Dou Liyang wrote: > Hi Baoquan, > > At 02/07/2018 08:45 PM, Baoquan He wrote: > > On 02/07/18 at 08:34pm, Dou Liyang wrote: > > > > > > > > > At 02/07/2018 08:27 PM, Baoquan He wrote: > > > > On 02/07/18 at 08:17pm, Dou Liyang wrote: > > > > > Hi Baoquan, > > > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/08/18 at 09:14am, Dou Liyang wrote: > Hi Baoquan, > > At 02/07/2018 08:45 PM, Baoquan He wrote: > > On 02/07/18 at 08:34pm, Dou Liyang wrote: > > > > > > > > > At 02/07/2018 08:27 PM, Baoquan He wrote: > > > > On 02/07/18 at 08:17pm, Dou Liyang wrote: > > > > > Hi Baoquan, > > > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Baoquan, At 02/07/2018 08:45 PM, Baoquan He wrote: On 02/07/18 at 08:34pm, Dou Liyang wrote: At 02/07/2018 08:27 PM, Baoquan He wrote: On 02/07/18 at 08:17pm, Dou Liyang wrote: Hi Baoquan, At 02/07/2018 08:08 PM, Baoquan He wrote: On 02/07/18 at 08:00pm, Dou Liyang wrote: Hi

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Baoquan, At 02/07/2018 08:45 PM, Baoquan He wrote: On 02/07/18 at 08:34pm, Dou Liyang wrote: At 02/07/2018 08:27 PM, Baoquan He wrote: On 02/07/18 at 08:17pm, Dou Liyang wrote: Hi Baoquan, At 02/07/2018 08:08 PM, Baoquan He wrote: On 02/07/18 at 08:00pm, Dou Liyang wrote: Hi

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 08:34pm, Dou Liyang wrote: > > > At 02/07/2018 08:27 PM, Baoquan He wrote: > > On 02/07/18 at 08:17pm, Dou Liyang wrote: > > > Hi Baoquan, > > > > > > At 02/07/2018 08:08 PM, Baoquan He wrote: > > > > On 02/07/18 at 08:00pm, Dou Liyang wrote: > > > > > Hi Kirill,Mike > > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 08:34pm, Dou Liyang wrote: > > > At 02/07/2018 08:27 PM, Baoquan He wrote: > > On 02/07/18 at 08:17pm, Dou Liyang wrote: > > > Hi Baoquan, > > > > > > At 02/07/2018 08:08 PM, Baoquan He wrote: > > > > On 02/07/18 at 08:00pm, Dou Liyang wrote: > > > > > Hi Kirill,Mike > > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

At 02/07/2018 08:27 PM, Baoquan He wrote: On 02/07/18 at 08:17pm, Dou Liyang wrote: Hi Baoquan, At 02/07/2018 08:08 PM, Baoquan He wrote: On 02/07/18 at 08:00pm, Dou Liyang wrote: Hi Kirill,Mike At 02/07/2018 06:45 PM, Mike Galbraith wrote: On Wed, 2018-02-07 at 13:41 +0300, Kirill A.

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

At 02/07/2018 08:27 PM, Baoquan He wrote: On 02/07/18 at 08:17pm, Dou Liyang wrote: Hi Baoquan, At 02/07/2018 08:08 PM, Baoquan He wrote: On 02/07/18 at 08:00pm, Dou Liyang wrote: Hi Kirill,Mike At 02/07/2018 06:45 PM, Mike Galbraith wrote: On Wed, 2018-02-07 at 13:41 +0300, Kirill A.

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 08:17pm, Dou Liyang wrote: > Hi Baoquan, > > At 02/07/2018 08:08 PM, Baoquan He wrote: > > On 02/07/18 at 08:00pm, Dou Liyang wrote: > > > Hi Kirill,Mike > > > > > > At 02/07/2018 06:45 PM, Mike Galbraith wrote: > > > > On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote:

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 08:17pm, Dou Liyang wrote: > Hi Baoquan, > > At 02/07/2018 08:08 PM, Baoquan He wrote: > > On 02/07/18 at 08:00pm, Dou Liyang wrote: > > > Hi Kirill,Mike > > > > > > At 02/07/2018 06:45 PM, Mike Galbraith wrote: > > > > On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote:

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Baoquan, At 02/07/2018 08:08 PM, Baoquan He wrote: On 02/07/18 at 08:00pm, Dou Liyang wrote: Hi Kirill,Mike At 02/07/2018 06:45 PM, Mike Galbraith wrote: On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: Hi All, I

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Baoquan, At 02/07/2018 08:08 PM, Baoquan He wrote: On 02/07/18 at 08:00pm, Dou Liyang wrote: Hi Kirill,Mike At 02/07/2018 06:45 PM, Mike Galbraith wrote: On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: Hi All, I

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 08:00pm, Dou Liyang wrote: > Hi Kirill,Mike > > At 02/07/2018 06:45 PM, Mike Galbraith wrote: > > On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: > > > On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: > > > > Hi All, > > > > > > > > I met the makedumpfile

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 08:00pm, Dou Liyang wrote: > Hi Kirill,Mike > > At 02/07/2018 06:45 PM, Mike Galbraith wrote: > > On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: > > > On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: > > > > Hi All, > > > > > > > > I met the makedumpfile

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Kirill,Mike At 02/07/2018 06:45 PM, Mike Galbraith wrote: On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: Hi All, I met the makedumpfile failed in the upstream kernel which contained this patch. Did I missed

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Kirill,Mike At 02/07/2018 06:45 PM, Mike Galbraith wrote: On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: Hi All, I met the makedumpfile failed in the upstream kernel which contained this patch. Did I missed

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 05:25pm, Dou Liyang wrote: > Hi All, > > I met the makedumpfile failed in the upstream kernel which contained > this patch. Did I missed something else? readmem: Can't convert a virtual address(88007ffd7000) to physical Should not related to this patch. Otherwise your code

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 02/07/18 at 05:25pm, Dou Liyang wrote: > Hi All, > > I met the makedumpfile failed in the upstream kernel which contained > this patch. Did I missed something else? readmem: Can't convert a virtual address(88007ffd7000) to physical Should not related to this patch. Otherwise your code

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: > On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: > > Hi All, > > > > I met the makedumpfile failed in the upstream kernel which contained > > this patch. Did I missed something else? > > None I'm aware of. > > Is there a

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, 2018-02-07 at 13:41 +0300, Kirill A. Shutemov wrote: > On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: > > Hi All, > > > > I met the makedumpfile failed in the upstream kernel which contained > > this patch. Did I missed something else? > > None I'm aware of. > > Is there a

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: > Hi All, > > I met the makedumpfile failed in the upstream kernel which contained > this patch. Did I missed something else? None I'm aware of. Is there a reason to suspect that the issue is related to the bug this patch fixed? --

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, Feb 07, 2018 at 05:25:05PM +0800, Dou Liyang wrote: > Hi All, > > I met the makedumpfile failed in the upstream kernel which contained > this patch. Did I missed something else? None I'm aware of. Is there a reason to suspect that the issue is related to the bug this patch fixed? --

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi All, I met the makedumpfile failed in the upstream kernel which contained this patch. Did I missed something else? In fedora27 host: [douly@localhost code]$ ./makedumpfile -d 31 --message-level 31 -x vmlinux_4.15+ vmcore_4.15+_from_cp_command vmcore_4.15+ sadump: does not have partition

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi All, I met the makedumpfile failed in the upstream kernel which contained this patch. Did I missed something else? In fedora27 host: [douly@localhost code]$ ./makedumpfile -d 31 --message-level 31 -x vmlinux_4.15+ vmcore_4.15+_from_cp_command vmcore_4.15+ sadump: does not have partition

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/25/18 at 06:50pm, Kirill A. Shutemov wrote: > On Wed, Jan 17, 2018 at 01:24:54PM +0800, Baoquan He wrote: > > Hi Kirill, > > > > I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both > > kexec and kdump reset to BIOS immediately after triggering. I saw your > > patch adding

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/25/18 at 06:50pm, Kirill A. Shutemov wrote: > On Wed, Jan 17, 2018 at 01:24:54PM +0800, Baoquan He wrote: > > Hi Kirill, > > > > I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both > > kexec and kdump reset to BIOS immediately after triggering. I saw your > > patch adding

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, Jan 17, 2018 at 01:24:54PM +0800, Baoquan He wrote: > Hi Kirill, > > I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both > kexec and kdump reset to BIOS immediately after triggering. I saw your > patch adding 5-level paging support for kexec. Wonder if your test >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, Jan 17, 2018 at 01:24:54PM +0800, Baoquan He wrote: > Hi Kirill, > > I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both > kexec and kdump reset to BIOS immediately after triggering. I saw your > patch adding 5-level paging support for kexec. Wonder if your test >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Kirill, I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both kexec and kdump reset to BIOS immediately after triggering. I saw your patch adding 5-level paging support for kexec. Wonder if your test succeeded to jump into kexec/kdump kernel, and what else I need to make it. By

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

Hi Kirill, I setup qemu 2.9.0 to test 5-level on kexec/kdump support. While both kexec and kdump reset to BIOS immediately after triggering. I saw your patch adding 5-level paging support for kexec. Wonder if your test succeeded to jump into kexec/kdump kernel, and what else I need to make it. By

RE: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

>Hm, this fix means that the vmlinux symbol table and vmcoreinfo have >different values for mem_section. That seems... odd. I had to patch >makedumpfile to fix the case of an explicit vmlinux being passed on the >command line (which I realized I don't need to do, but it should still >work): Looks

RE: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

>Hm, this fix means that the vmlinux symbol table and vmcoreinfo have >different values for mem_section. That seems... odd. I had to patch >makedumpfile to fix the case of an explicit vmlinux being passed on the >command line (which I realized I don't need to do, but it should still >work): Looks

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Jan 12, 2018 at 08:55:49AM +0800, Dave Young wrote: > On 01/10/18 at 02:16pm, Kirill A. Shutemov wrote: > > On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > > > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > > > On Tue, Jan 09, 2018 at 03:24:40PM

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Jan 12, 2018 at 08:55:49AM +0800, Dave Young wrote: > On 01/10/18 at 02:16pm, Kirill A. Shutemov wrote: > > On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > > > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > > > On Tue, Jan 09, 2018 at 03:24:40PM

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/10/18 at 02:16pm, Kirill A. Shutemov wrote: > On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > > > On 01/09/18 at 01:41pm, Baoquan He

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/10/18 at 02:16pm, Kirill A. Shutemov wrote: > On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > > > On 01/09/18 at 01:41pm, Baoquan He

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/10/18 at 02:16pm, Kirill A. Shutemov wrote: > On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > > > On 01/09/18 at 01:41pm, Baoquan He

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/10/18 at 02:16pm, Kirill A. Shutemov wrote: > On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > > > On 01/09/18 at 01:41pm, Baoquan He

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > > On 01/09/18 at 01:41pm, Baoquan He wrote: > > > > On 01/09/18 at 09:09am, Dave Young wrote: > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Wed, Jan 10, 2018 at 03:08:04AM +, Dave Young wrote: > On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > > On 01/09/18 at 01:41pm, Baoquan He wrote: > > > > On 01/09/18 at 09:09am, Dave Young wrote: > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > On 01/09/18 at 01:41pm, Baoquan He wrote: > > > On 01/09/18 at 09:09am, Dave Young wrote: > > > > > > > As for the macro name, VMCOREINFO_SYMBOL_ARRAY sounds

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Tue, Jan 09, 2018 at 12:05:52PM +0300, Kirill A. Shutemov wrote: > On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > > On 01/09/18 at 01:41pm, Baoquan He wrote: > > > On 01/09/18 at 09:09am, Dave Young wrote: > > > > > > > As for the macro name, VMCOREINFO_SYMBOL_ARRAY sounds

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > On 01/09/18 at 01:41pm, Baoquan He wrote: > > On 01/09/18 at 09:09am, Dave Young wrote: > > > > > As for the macro name, VMCOREINFO_SYMBOL_ARRAY sounds better. Yep, that's better. > > I still think using vmcoreinfo_append_str is

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Tue, Jan 09, 2018 at 03:24:40PM +0800, Dave Young wrote: > On 01/09/18 at 01:41pm, Baoquan He wrote: > > On 01/09/18 at 09:09am, Dave Young wrote: > > > > > As for the macro name, VMCOREINFO_SYMBOL_ARRAY sounds better. Yep, that's better. > > I still think using vmcoreinfo_append_str is

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/09/18 at 01:41pm, Baoquan He wrote: > On 01/09/18 at 09:09am, Dave Young wrote: > > On 01/09/18 at 03:13am, Kirill A. Shutemov wrote: > > > On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > > > > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/09/18 at 01:41pm, Baoquan He wrote: > On 01/09/18 at 09:09am, Dave Young wrote: > > On 01/09/18 at 03:13am, Kirill A. Shutemov wrote: > > > On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > > > > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/09/18 at 09:09am, Dave Young wrote: > On 01/09/18 at 03:13am, Kirill A. Shutemov wrote: > > On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > > > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > > > > > hi Kirill, > > > > > > > > As Mike reported it

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/09/18 at 09:09am, Dave Young wrote: > On 01/09/18 at 03:13am, Kirill A. Shutemov wrote: > > On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > > > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > > > > > hi Kirill, > > > > > > > > As Mike reported it

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Tue, 2018-01-09 at 03:13 +0300, Kirill A. Shutemov wrote: > > Mike, could you test this? (On top of the rest of the fixes.) homer:..crash/2018-01-09-04:25 # ll total 1863604 -rw--- 1 root root 66255 Jan 9 04:25 dmesg.txt -rw-r--r-- 1 root root182 Jan 9 04:25 README.txt

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Tue, 2018-01-09 at 03:13 +0300, Kirill A. Shutemov wrote: > > Mike, could you test this? (On top of the rest of the fixes.) homer:..crash/2018-01-09-04:25 # ll total 1863604 -rw--- 1 root root 66255 Jan 9 04:25 dmesg.txt -rw-r--r-- 1 root root182 Jan 9 04:25 README.txt

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/09/18 at 03:13am, Kirill A. Shutemov wrote: > On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > > > hi Kirill, > > > > > > As Mike reported it below, your 5-level paging related upstream commit > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 01/09/18 at 03:13am, Kirill A. Shutemov wrote: > On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > > > hi Kirill, > > > > > > As Mike reported it below, your 5-level paging related upstream commit > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > hi Kirill, > > > > As Mike reported it below, your 5-level paging related upstream commit > > 83e3c48729d9 and all its followup fixes: > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 08:46:53PM +0300, Kirill A. Shutemov wrote: > On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > > > hi Kirill, > > > > As Mike reported it below, your 5-level paging related upstream commit > > 83e3c48729d9 and all its followup fixes: > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > hi Kirill, > > As Mike reported it below, your 5-level paging related upstream commit > 83e3c48729d9 and all its followup fixes: > > 83e3c48729d9: mm/sparsemem: Allocate mem_section at runtime for > CONFIG_SPARSEMEM_EXTREME=y >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 04:04:44PM +, Ingo Molnar wrote: > > hi Kirill, > > As Mike reported it below, your 5-level paging related upstream commit > 83e3c48729d9 and all its followup fixes: > > 83e3c48729d9: mm/sparsemem: Allocate mem_section at runtime for > CONFIG_SPARSEMEM_EXTREME=y >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

hi Kirill, As Mike reported it below, your 5-level paging related upstream commit 83e3c48729d9 and all its followup fixes: 83e3c48729d9: mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y 629a359bdb0e: mm/sparsemem: Fix ARM64 boot crash when

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

hi Kirill, As Mike reported it below, your 5-level paging related upstream commit 83e3c48729d9 and all its followup fixes: 83e3c48729d9: mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y 629a359bdb0e: mm/sparsemem: Fix ARM64 boot crash when

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, 2018-01-08 at 09:33 +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 08, 2018 at 09:15:33AM +0100, Mike Galbraith wrote: > > > > It was part of the prep for the KTPI code from what I can tell. If you > > > think it should be reverted, just let me know and I'll be glad to do so. > > > > No

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, 2018-01-08 at 09:33 +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 08, 2018 at 09:15:33AM +0100, Mike Galbraith wrote: > > > > It was part of the prep for the KTPI code from what I can tell. If you > > > think it should be reverted, just let me know and I'll be glad to do so. > > > > No

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 10:10:44AM +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 08, 2018 at 09:47:23AM +0100, Michal Hocko wrote: > > On Mon 08-01-18 08:53:08, Greg KH wrote: > > > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > > > On Sun 07-01-18 13:44:02, Mike Galbraith

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 10:10:44AM +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 08, 2018 at 09:47:23AM +0100, Michal Hocko wrote: > > On Mon 08-01-18 08:53:08, Greg KH wrote: > > > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > > > On Sun 07-01-18 13:44:02, Mike Galbraith

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 09:47:23AM +0100, Michal Hocko wrote: > On Mon 08-01-18 08:53:08, Greg KH wrote: > > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 09:47:23AM +0100, Michal Hocko wrote: > On Mon 08-01-18 08:53:08, Greg KH wrote: > > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon 08-01-18 08:53:08, Greg KH wrote: > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > > > On Sun, Jan 07, 2018

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon 08-01-18 08:53:08, Greg KH wrote: > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > > > On Sun, Jan 07, 2018

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 09:15:33AM +0100, Mike Galbraith wrote: > On Mon, 2018-01-08 at 08:53 +0100, Greg Kroah-Hartman wrote: > > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > > On Sun, 2018-01-07 at 11:18 +0100, Michal

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, Jan 08, 2018 at 09:15:33AM +0100, Mike Galbraith wrote: > On Mon, 2018-01-08 at 08:53 +0100, Greg Kroah-Hartman wrote: > > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > > On Sun, 2018-01-07 at 11:18 +0100, Michal

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, 2018-01-08 at 08:53 +0100, Greg Kroah-Hartman wrote: > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Mon, 2018-01-08 at 08:53 +0100, Greg Kroah-Hartman wrote: > On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, Jan 07, 2018 at 02:23:09PM +0100, Michal Hocko wrote: > On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun 07-01-18 13:44:02, Mike Galbraith wrote: > On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > > On Sun 07-01-18 10:11:15, Greg KH wrote: > > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > On Sun 07-01-18 10:11:15, Greg KH wrote: > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > 4.14-stable review patch. If anyone has any objections,

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, 2018-01-07 at 11:18 +0100, Michal Hocko wrote: > On Sun 07-01-18 10:11:15, Greg KH wrote: > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > 4.14-stable review patch. If anyone has any objections,

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, Jan 07, 2018 at 11:18:47AM +0100, Michal Hocko wrote: > On Sun 07-01-18 10:11:15, Greg KH wrote: > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > 4.14-stable review patch. If anyone has any

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, Jan 07, 2018 at 11:18:47AM +0100, Michal Hocko wrote: > On Sun 07-01-18 10:11:15, Greg KH wrote: > > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > > 4.14-stable review patch. If anyone has any

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun 07-01-18 10:11:15, Greg KH wrote: > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > 4.14-stable review patch. If anyone has any objections, please let me > > > know. > > > > FYI, this broke kdump, or

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun 07-01-18 10:11:15, Greg KH wrote: > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > 4.14-stable review patch. If anyone has any objections, please let me > > > know. > > > > FYI, this broke kdump, or

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, 2018-01-07 at 10:11 +0100, Greg Kroah-Hartman wrote: > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > 4.14-stable review patch. If anyone has any objections, please let me > > > know. > > > > FYI,

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, 2018-01-07 at 10:11 +0100, Greg Kroah-Hartman wrote: > On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > > 4.14-stable review patch. If anyone has any objections, please let me > > > know. > > > > FYI,

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > FYI, this broke kdump, or rather the makedumpfile part thereof. >  Forward looking

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Sun, Jan 07, 2018 at 06:14:22AM +0100, Mike Galbraith wrote: > On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > FYI, this broke kdump, or rather the makedumpfile part thereof. >  Forward looking

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. FYI, this broke kdump, or rather the makedumpfile part thereof.  Forward looking wreckage is par for the kdump course, but... > -- > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, 2017-12-22 at 09:45 +0100, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. FYI, this broke kdump, or rather the makedumpfile part thereof.  Forward looking wreckage is par for the kdump course, but... > -- > >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Dec 22, 2017 at 08:22:09PM +0530, Naresh Kamboju wrote: > On 22 December 2017 at 19:48, Dan Rue wrote: > > On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: > >> 4.14-stable review patch. If anyone has any objections, please let me > >> know. > >> >

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Dec 22, 2017 at 08:22:09PM +0530, Naresh Kamboju wrote: > On 22 December 2017 at 19:48, Dan Rue wrote: > > On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: > >> 4.14-stable review patch. If anyone has any objections, please let me > >> know. > >> > >>

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Dec 22, 2017 at 08:18:10AM -0600, Dan Rue wrote: > On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Kirill A. Shutemov

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Dec 22, 2017 at 08:18:10AM -0600, Dan Rue wrote: > On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: > > 4.14-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Kirill A. Shutemov > > > > commit

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 22 December 2017 at 19:48, Dan Rue wrote: > On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: >> 4.14-stable review patch. If anyone has any objections, please let me know. >> >> -- >> >> From: Kirill A. Shutemov

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On 22 December 2017 at 19:48, Dan Rue wrote: > On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: >> 4.14-stable review patch. If anyone has any objections, please let me know. >> >> -- >> >> From: Kirill A. Shutemov >> >> commit

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Kirill A. Shutemov > > commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 upstream.

Re: [PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

On Fri, Dec 22, 2017 at 09:45:08AM +0100, Greg Kroah-Hartman wrote: > 4.14-stable review patch. If anyone has any objections, please let me know. > > -- > > From: Kirill A. Shutemov > > commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 upstream. > > Size of the mem_section[]

[PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 upstream. Size of the mem_section[] array depends on the size of the physical address

[PATCH 4.14 023/159] mm/sparsemem: Allocate mem_section at runtime for CONFIG_SPARSEMEM_EXTREME=y

4.14-stable review patch. If anyone has any objections, please let me know. -- From: Kirill A. Shutemov commit 83e3c48729d9ebb7af5a31a504f3fd6aff0348c4 upstream. Size of the mem_section[] array depends on the size of the physical address space. In preparation for boot-time