[PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

2016-12-07 Thread zhongjiang
From: zhong jiang A soft lookup will occur when I run trinity in syscall kexec_load. the corresponding stack information is as follows. [ 237.235937] BUG: soft lockup - CPU#6 stuck for 22s! [trinity-c6:13859] [ 237.242699] Kernel panic - not syncing: softlockup: hung tasks [ 237.248573] CPU:

[PATCH] kexec: add cond_resched into kimage_alloc_crash_control_pages

2016-12-07 Thread zhongjiang
From: zhong jiang A soft lookup will occur when I run trinity in syscall kexec_load. the corresponding stack information is as follows. [ 237.235937] BUG: soft lockup - CPU#6 stuck for 22s! [trinity-c6:13859] [ 237.242699] Kernel panic - not syncing: softlockup: hung tasks [ 237.248573] CPU:

[PATCH v2] kexec: add resriction on the kexec_load

2016-07-21 Thread zhongjiang
From: zhong jiang I hit the following question when run trinity in my system. The kernel is 3.4 version. but the mainline have same question to be solved. The root cause is the segment size is too large, it can expand the most of the area or the whole memory, therefore, it may waste an amount of

[PATCH v2] kexec: add resriction on the kexec_load

2016-07-21 Thread zhongjiang
From: zhong jiang I hit the following question when run trinity in my system. The kernel is 3.4 version. but the mainline have same question to be solved. The root cause is the segment size is too large, it can expand the most of the area or the whole memory, therefore, it may waste an amount of

[PATCH] kexec: add resriction on the kexec_load

2016-07-19 Thread zhongjiang
From: zhong jiang I hit the following question when run trinity in my system. The kernel is 3.4 version. but the mainline have same question to be solved. The root cause is the segment size is too large, it can expand the most of the area or the whole memory, therefore, it may waste an amount of

[PATCH] kexec: add resriction on the kexec_load

2016-07-18 Thread zhongjiang
From: zhong jiang I hit the following question when run trinity in my system. The kernel is 3.4 version. but the mainline have same question to be solved. The root cause is the segment size is too large, it can expand the most of the area or the whole memory, therefore, it may waste an amount of

[PATCH 2/2] kexec: add a pmd huge entry condition during the page table

2016-07-11 Thread zhongjiang
From: zhong jiang when image is loaded into kernel, we need set up page table for it. and all valid pfn also set up new mapping. it will tend to establish a pmd page table in the form of a large page if pud_present is true. relocate_kernel points to code segment can locate in the pmd huge entr

[PATCH 1/2] kexec: remove unnecessary unusable_pages

2016-07-11 Thread zhongjiang
From: zhong jiang In general, kexec alloc pages from buddy system, it cannot exceed the physical address in the system. The patch just remove this unnecessary code, no functional change. Signed-off-by: zhong jiang --- include/linux/kexec.h | 1 - kernel/kexec_core.c | 13 - 2 f