On Wed, Sep 19, 2018 at 08:52:49PM +0800, Lianbo Jiang wrote:
...
> In fact, we should get the resource A and B when we walk through the
> whole tree, but it only gets the resource A, the resource B is missed.
>
> Signed-off-by: Dave Young
> Signed-off-by: Lianbo Jiang
Before looking at
E820 reserved ranges is useful in kdump kernel, we have added this in
kexec-tools code.
One reason is PCI mmconf (extended mode) requires reserved region otherwise
it falls back to legacy mode.
Furthermore, when AMD SME kdump support, it needs to map dmi table area as
unencrypted. For normal
E820 reserved ranges is useful in kdump kernel, we have added this in
kexec-tools code.
One reason is PCI mmconf (extended mode) requires reserved region
otherwise it falls back to legacy mode.
When AMD SME kdump support, it needs to map dmi table area as unencrypted.
For normal boot these
When we walk through iomem resources by calling walk_iomem_res_desc(),
the values of the function parameter may be modified in the while loop
of __walk_iomem_res_desc(), which will cause us to not get the desired
result in some cases.
At present, it only restores the original value of res->end,
kdump use walk_iomem_res_desc to iterate io resources then add 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 need an extra
checking in memmap_entry_callback() to
kexec.h and slab.h have duplicated include. hence just remove
redundant file.
Signed-off-by: zhong jiang
---
kernel/kexec_file.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/kernel/kexec_file.c b/kernel/kexec_file.c
index c6a3b68..35cf0ad 100644
--- a/kernel/kexec_file.c
+++
