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: [ANNOUNCE] kexec-tools v2.0.14 preparation

On 12/07/16 at 11:59am, Simon Horman wrote: > On Wed, Dec 07, 2016 at 05:47:17PM +0800, Dave Young wrote: > > On 12/02/16 at 09:24am, Simon Horman wrote: > > > Hi all, > > > > > > I am planning to release kexec-tools v2.0.14 around the time that > > > the v4.9 kernel is released. > > > > > > I

[PATCH] kexec-tools/x86: get_kernel_vaddr_and_size off-by-one fix

I got below error while tesing kexec -p: "Can't find kernel text map area from kcore" The case is the pt_load start addr was same as stext_sym. The checking code should really be saddr <= stext_sym so that the right pt_load area includes stext_sym can be matched. This was not reported by people

[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

Re: [PATCH] kexec: add cond_resched into kimage_alloc_crash_control_pages

On 2016/12/8 9:50, Eric W. Biederman wrote: > 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. > Overall that looks reasonable.

Re: [PATCH] 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. Overall that looks reasonable. Why only every 256 page and not call cond_resched

Re: [PATCH Makedumpfile 00/10] arm64 cleanup and kaslr support

Works great for 4l 4k pages. Tested-by: Sameer Goel On 10/25/2016 1:22 AM, Pratyush Anand wrote: These patches were lying in my tree for quite some time now. VMCOREINFO numbers/symbols used in these patches have been made part of kdump kernel patches for last few

[PATCH] arm64: Fix initrd requierements

The initrd doesn't need to be aligend to 1 GB, which breaks kexec for system with RAM <= 1 GB. Instead the memory size between the kernel start rounded down to 1 GB and the end of the initrd rounded up to 1 GB can't be bigger then 32 GB. Signed-off-by: Matthias Brugger ---

[PATCH] 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

Re: [ANNOUNCE] kexec-tools v2.0.14 preparation

On Wed, Dec 07, 2016 at 05:47:17PM +0800, Dave Young wrote: > On 12/02/16 at 09:24am, Simon Horman wrote: > > Hi all, > > > > I am planning to release kexec-tools v2.0.14 around the time that > > the v4.9 kernel is released. > > > > I would like to ask interested parties to send any patches they

[PATCHv5 00/11] CONFIG_DEBUG_VIRTUAL for arm64

Hi, This is v5 of the series to add CONFIG_DEBUG_VIRTUAL for arm64. This mostly contains minor fixups including adding a few extra headers around and splitting things out into a few more sub-patches. With a few more acks I think this should be ready to go. More testing is always appreciated

Re: [ANNOUNCE] kexec-tools v2.0.14 preparation

On 12/02/16 at 09:24am, Simon Horman wrote: > Hi all, > > I am planning to release kexec-tools v2.0.14 around the time that > the v4.9 kernel is released. > > I would like to ask interested parties to send any patches they would like > included in v2.0.14 within one week so that I can make an rc