Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/19/2016 at 11:23 AM, Baoquan He wrote: > On 12/09/16 at 03:16pm, Xunlei Pang wrote: >> On 12/09/2016 at 01:13 PM, zhong jiang wrote: >>> On 2016/12/8 17:41, Xunlei Pang wrote: On 12/08/2016 at 10:37 AM, zhongjiang wrote: > From: zhong jiang > > A soft

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/19/2016 at 11:23 AM, Baoquan He wrote: > On 12/09/16 at 03:16pm, Xunlei Pang wrote: >> On 12/09/2016 at 01:13 PM, zhong jiang wrote: >>> On 2016/12/8 17:41, Xunlei Pang wrote: On 12/08/2016 at 10:37 AM, zhongjiang wrote: > From: zhong jiang > > A soft lookup will occur when

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/09/16 at 03:16pm, Xunlei Pang wrote: > On 12/09/2016 at 01:13 PM, zhong jiang wrote: > > On 2016/12/8 17:41, Xunlei Pang wrote: > >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: > >>> From: zhong jiang > >>> > >>> A soft lookup will occur when I run trinity in syscall

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/09/16 at 03:16pm, Xunlei Pang wrote: > On 12/09/2016 at 01:13 PM, zhong jiang wrote: > > On 2016/12/8 17:41, Xunlei Pang wrote: > >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: > >>> From: zhong jiang > >>> > >>> A soft lookup will occur when I run trinity in syscall kexec_load. > >>> the

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/09/2016 at 01:13 PM, zhong jiang wrote: > On 2016/12/8 17:41, Xunlei Pang wrote: >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: >>> From: zhong jiang >>> >>> A soft lookup will occur when I run trinity in syscall kexec_load. >>> the corresponding stack information is

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/09/2016 at 01:13 PM, zhong jiang wrote: > On 2016/12/8 17:41, Xunlei Pang wrote: >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: >>> From: zhong jiang >>> >>> A soft lookup will occur when I run trinity in syscall kexec_load. >>> the corresponding stack information is as follows. >>> >>> [

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/9 13:19, Eric W. Biederman wrote: > zhong jiang writes: > >> On 2016/12/8 17:41, Xunlei Pang wrote: >>> On 12/08/2016 at 10:37 AM, zhongjiang wrote: From: zhong jiang > [snip] diff --git a/kernel/kexec_core.c

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/9 13:19, Eric W. Biederman wrote: > zhong jiang writes: > >> On 2016/12/8 17:41, Xunlei Pang wrote: >>> On 12/08/2016 at 10:37 AM, zhongjiang wrote: From: zhong jiang > [snip] diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c index 5616755..bfc9621 100644

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhong jiang writes: > On 2016/12/8 17:41, Xunlei Pang wrote: >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: >>> From: zhong jiang >>> [snip] >>> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c >>> index 5616755..bfc9621 100644 >>> ---

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhong jiang writes: > On 2016/12/8 17:41, Xunlei Pang wrote: >> On 12/08/2016 at 10:37 AM, zhongjiang wrote: >>> From: zhong jiang >>> [snip] >>> diff --git a/kernel/kexec_core.c b/kernel/kexec_core.c >>> index 5616755..bfc9621 100644 >>> --- a/kernel/kexec_core.c >>> +++ b/kernel/kexec_core.c

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/8 17:41, Xunlei Pang wrote: > On 12/08/2016 at 10:37 AM, zhongjiang wrote: >> 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 -

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/8 17:41, Xunlei Pang wrote: > On 12/08/2016 at 10:37 AM, zhongjiang wrote: >> 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!

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/08/2016 at 10:37 AM, zhongjiang wrote: > 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] > [

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 12/08/2016 at 10:37 AM, zhongjiang wrote: > 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

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhongjiang writes: > From: zhong jiang > > A soft lookup will occur when I run trinity in syscall kexec_load. > the corresponding stack information is as follows. Acked-by: "Eric W. Biederman" > > [ 237.235937] BUG: soft

Re: [PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

zhongjiang writes: > From: zhong jiang > > A soft lookup will occur when I run trinity in syscall kexec_load. > the corresponding stack information is as follows. Acked-by: "Eric W. Biederman" > > [ 237.235937] BUG: soft lockup - CPU#6 stuck for 22s! [trinity-c6:13859] > [ 237.242699]

[PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

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

[PATCH v2] kexec: add cond_resched into kimage_alloc_crash_control_pages

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: