Re: [PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table

On 11/07/18 at 01:00pm, Lianbo Jiang wrote: > E820 reserved ranges is useful in kdump kernel, it has been added in > kexec-tools code. > > One reason is PCI mmconf (extended mode) requires reserved region otherwise > it falls back to legacy mode, and also outputs the following kernel log. OK, it

Re: [PATCH 1/2 v5] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name

Hi Lianbo, On 11/07/18 at 01:00pm, Lianbo Jiang wrote: > kdump uses walk_iomem_res_desc() to iterate io resources, then adds matched > desc to e820 table for kdump kernel. > > But IORES_DESC_NONE resource type includes several different e820 types, As we discussed privately, better say more

[PATCH 1/2 v5] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name

kdump uses walk_iomem_res_desc() to iterate io resources, then adds matched desc to e820 table for kdump kernel. But IORES_DESC_NONE resource type includes several different e820 types, we need add exact e820 type to kdump kernel e820 table, thus it also needs an extra checking in

[PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table

E820 reserved ranges is useful in kdump kernel, it has been added in kexec-tools code. One reason is PCI mmconf (extended mode) requires reserved region otherwise it falls back to legacy mode, and also outputs the following kernel log. Example: .. [ 19.798354] PCI: MMCONFIG for domain

[PATCH 0/2 v5] add reserved e820 ranges to the kdump kernel e820 table

E820 reserved ranges is useful in kdump kernel, it has been added in kexec-tools code. One reason is PCI mmconf (extended mode) requires reserved region otherwise it falls back to legacy mode, and also outputs the following kernel log. Example: .. [ 19.798354] PCI: MMCONFIG for domain

Re: [PATCH v2 2/3] keys: export find_keyring_by_name()

Hi Nayna, On Fri, 2018-03-09 at 21:08 +0530, Nayna Jain wrote: > This patch exports the function find_keyring_by_name() to be used by > other subsystems. Looking this patch over again, I realize that exported functions must be prefixed with the subsystem name.  I'm also a bit concerned with

Re: [Bug Report] kdump crashes after latest EFI memblock changes on arm64 machines with large number of CPUs

On 6 November 2018 at 02:30, Will Deacon wrote: > On Fri, Nov 02, 2018 at 02:44:10AM +0530, Bhupesh Sharma wrote: >> With the latest EFI changes for memblock reservation across kdump >> kernel from Ard (Commit 71e0940d52e107748b270213a01d3b1546657d74 >> ["efi: honour memory reservations passed

Re: [PATCH] lockdown: allow kexec_file of unsigned images when not under lockdown

Hi Thadeu, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.19 next-20181102] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] lockdown: allow kexec_file of unsigned images when not under lockdown

Hi Thadeu, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.19 next-20181102] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: