Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr

2019-02-11 Thread Pingfan Liu
On Tue, Feb 12, 2019 at 4:48 AM Dave Young wrote: > > On 02/06/19 at 08:08pm, Dave Young wrote: > > On 02/05/19 at 09:15am, Borislav Petkov wrote: > > > On Mon, Feb 04, 2019 at 03:30:16PM -0700, Jerry Hoemann wrote: > > > > Is your objection only to the second fallback of allocating > > > > memory

Re: [PATCH] arm64, vmcoreinfo : Append 'MAX_USER_VA_BITS' and 'MAX_PHYSMEM_BITS' to vmcoreinfo

2019-02-11 Thread Bhupesh Sharma
Hi Kazu, On 02/04/2019 09:34 PM, Kazuhito Hagio wrote: On 1/30/2019 8:48 PM, Dave Young wrote: + more people On 01/30/19 at 05:53pm, Bhupesh Sharma wrote: With ARMv8.2-LVA and LPA architecture extensions, arm64 hardware which supports these extensions can support upto 52-bit virtual and 52-bit

Re: [PATCH] arm64, vmcoreinfo : Append 'MAX_USER_VA_BITS' and 'MAX_PHYSMEM_BITS' to vmcoreinfo

2019-02-11 Thread Bhupesh Sharma
Hi Robin, On 02/04/2019 09:01 PM, Robin Murphy wrote: On 04/02/2019 14:35, Bhupesh Sharma wrote: [...] Also hardcoding the PTE calculation to use the high address bit mask always will break the backward compatibility with older kernels (which don't support 52-bit address space extensions). N

RE: [PATCH] makedumpfile/arm64: Add support for ARMv8.2-LVA (52-bit user-space VA support)

2019-02-11 Thread Kazuhito Hagio
Hi Bhupesh, On 2/7/2019 2:52 PM, Bhupesh Sharma wrote: > With ARMv8.2-LVA architecture extension availability, arm64 hardware > which supports this extension can support upto 52-bit virtual > addresses. It is specially useful for having a 52-bit user-space virtual > address space while the kernel

Re: [PATCHv7] x86/kdump: bugfix, make the behavior of crashkernel=X consistent with kaslr

2019-02-11 Thread Dave Young
On 02/06/19 at 08:08pm, Dave Young wrote: > On 02/05/19 at 09:15am, Borislav Petkov wrote: > > On Mon, Feb 04, 2019 at 03:30:16PM -0700, Jerry Hoemann wrote: > > > Is your objection only to the second fallback of allocating > > > memory above >= 4GB? Or are you objecting to allocating from > > >