add reserved e820 ranges to the kdump kernel e820 table
Subsystems (3)
v5 cover 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 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 19.800653] [Firmware Info]: PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] not reserved in ACPI motherboard resources [ 19.800995] PCI: not using MMCONFIG
......
The correct kernel log is like this:
......
[ 0.082649] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 0.083610] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
......
Furthermore, when AMD SME kdump support, it needs to map dmi table area as decrypted. For normal boot, these ranges sit in e820 reserved ranges, thus the early ioremap code naturally map them as decrypted. If it also has same e820 reserve setup in kdump kernel then it will just work like normal kernel.
Kdump uses walk_iomem_res_desc to iterate resources, then adds matched desc to e820 table for the kdump kernel.
But IORES_DESC_NONE resource type includes several different e820 types, we need add exact e820 type to the kdump kernel e820 table, thus it also needs an extra checking in memmap_entry_callback() to match the e820 type and resource name.
Changes since v1:
1. Modified the value of flags to "0", when walking through the whole tree for e820 reserved ranges.
Changes since v2:
1. Modified the value of flags to "0", when walking through the whole tree for e820 reserved ranges.
2. Modified the invalid SOB chain issue.
Changes since v3:
1. Dropped [PATCH 1/3 v3] resource: fix an error which walks through iomem resources. Please refer to this commit <010a93bf97c7> "resource: Fix find_next_iomem_res() iteration issue"
Changes since v4:
1. Improve the patch log, and add kernel log.
Lianbo Jiang (2):
x86/kexec_file: add e820 entry in case e820 type string matches to io
resource name
x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table
arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/crash.c | 10 +++++++++- arch/x86/kernel/e820.c | 2 +- kernel/resource.c | 1 + 4 files changed, 13 insertions(+), 2 deletions(-)
Signature · 1 line
2.17.1
PATCH v5 1/2 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 memmap_entry_callback() to match the e820 type and resource name.
--- arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/crash.c | 6 +++++- arch/x86/kernel/e820.c | 2 +- kernel/resource.c | 1 + 4 files changed, 9 insertions(+), 2 deletions(-)
arch/x86/include/asm/e820/api.h +2 -0
@@ -42,6 +42,8 @@ extern void e820__register_nosave_regions(unsigned long limit_pfn);extern int e820__get_entry_type (u64 start,u64 end); +extern const char *e820_type_to_string (struct e820_entry *entry); +/* * Returns true iff the specified range [start,end) is completely contained inside * the ISA region.
arch/x86/kernel/crash.c +5 -1
@@ -37,6 +37,7 @@#include <asm/reboot.h> #include <asm/virtext.h> #include <asm/intel_pt.h> +#include <asm/e820/api.h> /* Used while preparing memory map entries for second kernel */ struct crash_memmap_data {
@@ -314,11 +315,14 @@ static int memmap_entry_callback(struct resource *res, void *arg)struct crash_memmap_data *cmd = arg;struct boot_params *params = cmd->params;struct e820_entry ei; +const char *name; ei.addr = res->start; ei.size =resource_size (res); ei.type = cmd->type; -add_e820_entry (params, &ei); + name =e820_type_to_string (&ei); +if (res->name && !strcmp (name, res->name)) +add_e820_entry (params, &ei);return 0 ; }
arch/x86/kernel/e820.c +1 -1
@@ -1011,7 +1011,7 @@ void __init e820__finish_early_params(void) } } -static const char *__init e820_type_to_string (struct e820_entry *entry) +const char *e820_type_to_string (struct e820_entry *entry) {switch (entry->type) {case E820_TYPE_RESERVED_KERN :/* Fall-through: */
kernel/resource.c +1 -0
@@ -366,6 +366,7 @@ static int find_next_iomem_res(resource_size_t start, resource_size_t end, res->end =min (end, p->end); res->flags = p->flags; res->desc = p->desc; + res->name = p->name;return 0 ; }
Signature · 1 line
2.17.1
Re: [PATCH 1/2 v5] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name
Hi Lianbo,
Quoted 4 lines · Lianbo Jiang
kdump uses
walk_iomem_res_desc()to iterate io resources, then adds matched desc to e820 table for kdump kernel.But
IORES_DESC_NONEresource type includes several different e820 types,
As we discussed privately, better say more clearly what is "IORES_DESC_NONE resource type includes several different e820 types".
You can tell:
When convert e820 type into iores descriptors, several e820 types are all converted to IORES_DESC_NONE in function e820_type_to_iores_desc().
Here may no need to list below code if you have told clearly what happened. Otherwise could you tell what it mean about the sentence:
"IORES_DESC_NONE resource type includes several different e820 types".
They are diffeent types, why one type includes another type, how does it include? Why it matters when one type includes another type? Why do you care?
static unsigned long __init e820_type_to_iores_desc(struct e820_entry *entry)
{
switch (entry->type) {
case E820_TYPE_ACPI: return IORES_DESC_ACPI_TABLES;
case E820_TYPE_NVS: return IORES_DESC_ACPI_NV_STORAGE;
case E820_TYPE_PMEM: return IORES_DESC_PERSISTENT_MEMORY;
case E820_TYPE_PRAM: return IORES_DESC_PERSISTENT_MEMORY_LEGACY;
case E820_TYPE_RESERVED_KERN: /* Fall-through: */
case E820_TYPE_RAM: /* Fall-through: */
case E820_TYPE_UNUSABLE: /* Fall-through: */
case E820_TYPE_RESERVED: /* Fall-through: */
default: return IORES_DESC_NONE;
}
}Quoted 1 line
we need add exact e820 type to kdump kernel e820 table, thus it also needs
Why we need add exact e820 type to kdump kernel e820 table? just because "IORES_DESC_NONE resource type includes several different e820 types"? Why we didn't need it before, why need it now?
Add it for what? Fix a bug/add a feature?
Quoted 2 lines
an extra checking in
memmap_entry_callback()to match the e820 type and resource name.
This paragraph only tells how you fix it. "IORES_DESC_NONE resource type includes several different e820 types" only tells a fact. So what's impacted by the including? Why i'ts impacted?
Quoted 79 lines
Suggested-by Dave Young <[email protected]>Signed-off-by Lianbo Jiang <[email protected]>--- arch/x86/include/asm/e820/api.h | 2 ++ arch/x86/kernel/crash.c | 6 +++++- arch/x86/kernel/e820.c | 2 +- kernel/resource.c | 1 + 4 files changed, 9 insertions(+), 2 deletions(-)arch/x86/include/asm/e820/api.h +2
-0@@ -42,6 +42,8 @@ extern void e820__register_nosave_regions(unsigned long limit_pfn);extern int e820__get_entry_type (u64 start,u64 end); +extern const char *e820_type_to_string (struct e820_entry *entry); +/* * Returns true iff the specified range [start,end) is completely contained inside * the ISA region. arch/x86/kernel/crash.c +5
-1@@ -37,6 +37,7 @@#include <asm/reboot.h> #include <asm/virtext.h> #include <asm/intel_pt.h> +#include <asm/e820/api.h> /* Used while preparing memory map entries for second kernel */ struct crash_memmap_data {@@ -314,11 +315,14 @@ static int memmap_entry_callback(struct resource *res, void *arg)struct crash_memmap_data *cmd = arg;struct boot_params *params = cmd->params;struct e820_entry ei; +const char *name; ei.addr = res->start; ei.size =resource_size (res); ei.type = cmd->type; -add_e820_entry (params, &ei); + name =e820_type_to_string (&ei); +if (res->name && !strcmp (name, res->name)) +add_e820_entry (params, &ei);return 0 ; }arch/x86/kernel/e820.c +1
-1@@ -1011,7 +1011,7 @@ void __init e820__finish_early_params(void) } } -static const char *__init e820_type_to_string (struct e820_entry *entry) +const char *e820_type_to_string (struct e820_entry *entry) {switch (entry->type) {case E820_TYPE_RESERVED_KERN :/* Fall-through: */ kernel/resource.c +1
-0@@ -366,6 +366,7 @@ static int find_next_iomem_res(resource_size_t start, resource_size_t end, res->end =min (end, p->end); res->flags = p->flags; res->desc = p->desc; + res->name = p->name;return 0 ; }Signature · 1 line
2.17.1
PATCH v5 2/2 x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table
In reply to Lianbo JiangE820 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 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 19.800653] [Firmware Info]: PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] not reserved in ACPI motherboard resources [ 19.800995] PCI: not using MMCONFIG
......
The correct kernel log is like this:
......
[ 0.082649] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 0.083610] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
......
Furthermore, when AMD SME kdump support, it needs to map dmi table area as decrypted. For normal boot, these ranges sit in e820 reserved ranges, thus the early ioremap code naturally map them as decrypted. If it also has same e820 reserve setup in kdump kernel then it will just work like normal kernel.
--- arch/x86/kernel/crash.c | 4 ++++ 1 file changed, 4 insertions(+)
arch/x86/kernel/crash.c +4 -0
@@ -384,6 +384,10 @@ int crash_setup_memmap_entries(struct kimage *image, struct boot_params *params)walk_iomem_res_desc (IORES_DESC_ACPI_NV_STORAGE , flags,0 ,-1 , &cmd, memmap_entry_callback); + cmd.type =E820_TYPE_RESERVED ; +walk_iomem_res_desc (IORES_DESC_NONE ,0 ,0 ,-1 , &cmd, + memmap_entry_callback); +/* Add crashk_low_res region */ if (crashk_low_res.end) { ei.addr = crashk_low_res.start;
Signature · 1 line
2.17.1
Re: [PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table
Quoted 5 lines · Lianbo Jiang
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 falls back to legacy mode, and also output kernel log, except of these, does it crash kernel? kdump kernel hang? Can we leave it if it only ouptut kernel log?
Quoted 12 lines
Example:
......[ 19.798354] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 19.800653] [Firmware Info]: PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] not reserved in ACPI motherboard resources [ 19.800995] PCI: not using MMCONFIG......
The correct kernel log is like this:
......[ 0.082649] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 0.083610] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Quoted 7 lines
......
Furthermore, when AMD SME kdump support, it needs to map dmi table area as decrypted. For normal boot, these ranges sit in e820 reserved ranges, thus the early ioremap code naturally map them as decrypted. If it also has same e820 reserve setup in kdump kernel then it will just work like normal kernel.
Why do we care? If don't fix, what's happening?
Lianbo, for a bug fix, please describe the problems. Then give out the analysis about root cause.
Quoted 25 lines
Suggested-by Dave Young <[email protected]>Signed-off-by Lianbo Jiang <[email protected]>--- arch/x86/kernel/crash.c | 4 ++++ 1 file changed, 4 insertions(+)arch/x86/kernel/crash.c +4
-0@@ -384,6 +384,10 @@ int crash_setup_memmap_entries(struct kimage *image, struct boot_params *params)walk_iomem_res_desc (IORES_DESC_ACPI_NV_STORAGE , flags,0 ,-1 , &cmd, memmap_entry_callback); + cmd.type =E820_TYPE_RESERVED ; +walk_iomem_res_desc (IORES_DESC_NONE ,0 ,0 ,-1 , &cmd, + memmap_entry_callback); +/* Add crashk_low_res region */ if (crashk_low_res.end) { ei.addr = crashk_low_res.start;Signature · 1 line
2.17.1
Re: [PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table
Quoted 31 lines · Baoquan He
Quoted 5 lines · Lianbo Jiang
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 falls back to legacy mode, and also output kernel log, except of these, does it crash kernel? kdump kernel hang? Can we leave it if it only ouptut kernel log?
Quoted 12 lines
Example:
......[ 19.798354] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 19.800653] [Firmware Info]: PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] not reserved in ACPI motherboard resources [ 19.800995] PCI: not using MMCONFIG......
The correct kernel log is like this:
......[ 0.082649] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 0.083610] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820Quoted 7 lines
......
Furthermore, when AMD SME kdump support, it needs to map dmi table area as decrypted. For normal boot, these ranges sit in e820 reserved ranges, thus the early ioremap code naturally map them as decrypted. If it also has same e820 reserve setup in kdump kernel then it will just work like normal kernel.
Quoted 5 lines
Why do we care? If don't fix, what's happening?
Lianbo, for a bug fix, please describe the problems. Then give out the analysis about root cause.
Thanks for your comment in detail.
In fact, these patches are really simple. As the subject mentioned, this patch [PATCH 2/2] adds the reserved e820 ranges to kdump kernel e820 table, and the first patch [PATCH 1/2] helps to exactly add the e820(E820_TYPE_RESERVED) type to kdump kernel e820 table, that is to say, it will filter out some unnecessary type(E820_TYPE_RAM/E820_TYPE_UNUSABLE/E820_TYPE_RESERVED_KERN).
At present, when we use the kexec to load the kernel image and initramfs(for
example: kexec -s -p xxxx), the latest kernel does not pass the e820 reserved ranges to the second kernel, which might produce two problems:
The first one is the MMCONFIG issue, although which does not make the system crash or hang, this issue is still a potential risk, because my test can't cover all cases due to resource constraints(Machine), and i'm not sure what it will happen on other machine.
The second issue is that the e820 reserved ranges do not setup in kdump kernel, which will cause some functions which are related to the e820 reserved ranges to become invalid. For example:
early_memremap()->
early_memremap_pgprot_adjust()->
memremap_should_map_decrypted()->e820__get_entry_type()
Please focus on these functions, early_memremap_pgprot_adjust() and memremap_should_map_decrypted().
In the first kernel, these ranges sit in e820 reserved ranges, so the memremap_should_map_decrypted() will return true, that is to say, the reserved memory is decrypted, then the early_memremap_pgprot_adjust() will call the pgprot_decrypted() to clear the memory encryption mask.
In the second kernel, because the e820 reserved ranges are not passed to the second kernel, these ranges don't sit in the e820 reserved ranges, so the the memremap_should_map_decrypted() will return false, that is to say, the reserved memory is encrypted, and then the early_memremap_pgprot_adjust() will also call the pgprot_encrypted() to set the memory encryption mask.
Obviously, in the second kernel, the e820 reserved memory is still decrypted, it has gone wrong. So, if don't fix, kdump won't work when we use the command(kexec -s -p xxx) to load the kernel image and initramfs.
Hope this helps.
Thanks,
Lianbo
pgprot_t __init early_memremap_pgprot_adjust(resource_size_t phys_addr,
unsigned long size, pgprot_t prot)
{
bool encrypted_prot;
if (!mem_encrypt_active())
return prot;
encrypted_prot = true;
//......
if (encrypted_prot && memremap_should_map_decrypted(phys_addr, size))
encrypted_prot = false;
return encrypted_prot ? pgprot_encrypted(prot)
: pgprot_decrypted(prot);
}static bool memremap_should_map_decrypted(resource_size_t phys_addr,
unsigned long size)
{
int is_pmem;
//......
/* Check if the address is outside kernel usable area */
switch (e820__get_entry_type(phys_addr, phys_addr + size - 1)) {
case E820_TYPE_RESERVED:
case E820_TYPE_ACPI:
case E820_TYPE_NVS:
case E820_TYPE_UNUSABLE:
/* For SEV, these areas are encrypted */
if (sev_active())
break;
/* Fallthrough */
case E820_TYPE_PRAM:
return true;
default:
break;
}
return false;
}Quoted 26 lines
Quoted 26 lines
Suggested-by Dave Young <[email protected]>Signed-off-by Lianbo Jiang <[email protected]>--- arch/x86/kernel/crash.c | 4 ++++ 1 file changed, 4 insertions(+)arch/x86/kernel/crash.c +4
-0@@ -384,6 +384,10 @@ int crash_setup_memmap_entries(struct kimage *image, struct boot_params *params)walk_iomem_res_desc (IORES_DESC_ACPI_NV_STORAGE , flags,0 ,-1 , &cmd, memmap_entry_callback); + cmd.type =E820_TYPE_RESERVED ; +walk_iomem_res_desc (IORES_DESC_NONE ,0 ,0 ,-1 , &cmd, + memmap_entry_callback); +/* Add crashk_low_res region */ if (crashk_low_res.end) { ei.addr = crashk_low_res.start;Signature · 1 line
2.17.1
Re: [PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table
Quoted 46 lines · lijiang
Quoted 31 lines · Baoquan He
Quoted 5 lines · Lianbo Jiang
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 falls back to legacy mode, and also output kernel log, except of these, does it crash kernel? kdump kernel hang? Can we leave it if it only ouptut kernel log?
Quoted 12 lines
Example:
......[ 19.798354] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 19.800653] [Firmware Info]: PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] not reserved in ACPI motherboard resources [ 19.800995] PCI: not using MMCONFIG......
The correct kernel log is like this:
......[ 0.082649] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000) [ 0.083610] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820Quoted 7 lines
......
Furthermore, when AMD SME kdump support, it needs to map dmi table area as decrypted. For normal boot, these ranges sit in e820 reserved ranges, thus the early ioremap code naturally map them as decrypted. If it also has same e820 reserve setup in kdump kernel then it will just work like normal kernel.
Quoted 5 lines
Why do we care? If don't fix, what's happening?
Lianbo, for a bug fix, please describe the problems. Then give out the analysis about root cause.
Thanks for your comment in detail.
In fact, these patches are really simple. As the subject mentioned, this patch [PATCH 2/2] adds the reserved e820 ranges to kdump kernel e820 table, and the first patch [PATCH 1/2] helps to exactly add the
e820(E820_TYPE_RESERVED)type to kdump kernel e820 table, that is to say, it will filter out some unnecessarytype(E820_TYPE_RAM/E820_TYPE_UNUSABLE/E820_TYPE_RESERVED_KERN).
Quoted 8 lines
At present, when we use the kexec to load the kernel image and initramfs(for
example: kexec -s -p xxxx), the latest kernel does not pass the e820 reserved ranges to the second kernel, which might produce two problems:The first one is the MMCONFIG issue, although which does not make the system crash or hang, this issue is still a potential risk, because my test can't cover all cases due to resource constraints(Machine), and i'm not sure what it will happen on other machine.
If a device is plugged in pci domain 1 then this device can not be recognized in kdump kernel in your case. For example if one want to dump to a network target, but the net card can not be recognized then vmcore can not be saved successfully
Thanks
Dave
Re: [PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table
In reply to lijiangQuoted 30 lines · lijiang
In fact, these patches are really simple. As the subject mentioned, this patch [PATCH 2/2] adds the reserved e820 ranges to kdump kernel e820 table, and the first patch [PATCH 1/2] helps to exactly add the
e820(E820_TYPE_RESERVED)type to kdump kernel e820 table, that is to say, it will filter out some unnecessarytype(E820_TYPE_RAM/E820_TYPE_UNUSABLE/E820_TYPE_RESERVED_KERN).At present, when we use the kexec to load the kernel image and initramfs(for
example: kexec -s -p xxxx), the latest kernel does not pass the e820 reserved ranges to the second kernel, which might produce two problems:The first one is the MMCONFIG issue, although which does not make the system crash or hang, this issue is still a potential risk, because my test can't cover all cases due to resource constraints(Machine), and i'm not sure what it will happen on other machine.
The second issue is that the e820 reserved ranges do not setup in kdump kernel, which will cause some functions which are related to the e820 reserved ranges to become invalid. For example:
early_memremap()->
early_memremap_pgprot_adjust()->
memremap_should_map_decrypted()->e820__get_entry_type()Please focus on these functions,
early_memremap_pgprot_adjust()andmemremap_should_map_decrypted().In the first kernel, these ranges sit in e820 reserved ranges, so the
memremap_should_map_decrypted()will return true, that is to say, the reserved memory is decrypted, then theearly_memremap_pgprot_adjust()will call thepgprot_decrypted()to clear the memory encryption mask.
Quoted 7 lines
In the second kernel, because the e820 reserved ranges are not passed to the second kernel, these ranges don't sit in the e820 reserved ranges, so the the
memremap_should_map_decrypted()will return false, that is to say, the reserved memory is encrypted, and then theearly_memremap_pgprot_adjust()will also call thepgprot_encrypted()to set the memory encryption mask.Obviously, in the second kernel, the e820 reserved memory is still decrypted, it has gone wrong. So, if don't fix, kdump won't work when we use the command(kexec -s -p xxx) to load the kernel image and initramfs.
Yes, this looks better. In fact, I searched cover-letter and both patch lg, didn't find anything to tell what will happen without these patchset. We should at least tell the patch is for cleanup/improvement/fix/feature. This "if don't fix, kdump won't work ..." is the sentence I first saw telling the sequence or the problem.
Please do not misunderstand those questions from me with unfriendly tone, words are cold and can't express emotions exactly, and appearance. Those questions are just meaning that people may get confusion from those places.
What: describe the problem you met. Why: tell the root cause How: how you fix it
This is what I usually use to write patch log. Just for your reference.
Thanks
Baoquan
Re: [PATCH 2/2 v5] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table
Quoted 45 lines · Baoquan He
Quoted 30 lines · lijiang
In fact, these patches are really simple. As the subject mentioned, this patch [PATCH 2/2] adds the reserved e820 ranges to kdump kernel e820 table, and the first patch [PATCH 1/2] helps to exactly add the
e820(E820_TYPE_RESERVED)type to kdump kernel e820 table, that is to say, it will filter out some unnecessarytype(E820_TYPE_RAM/E820_TYPE_UNUSABLE/E820_TYPE_RESERVED_KERN).At present, when we use the kexec to load the kernel image and initramfs(for
example: kexec -s -p xxxx), the latest kernel does not pass the e820 reserved ranges to the second kernel, which might produce two problems:The first one is the MMCONFIG issue, although which does not make the system crash or hang, this issue is still a potential risk, because my test can't cover all cases due to resource constraints(Machine), and i'm not sure what it will happen on other machine.
The second issue is that the e820 reserved ranges do not setup in kdump kernel, which will cause some functions which are related to the e820 reserved ranges to become invalid. For example:
early_memremap()->
early_memremap_pgprot_adjust()->
memremap_should_map_decrypted()->e820__get_entry_type()Please focus on these functions,
early_memremap_pgprot_adjust()andmemremap_should_map_decrypted().In the first kernel, these ranges sit in e820 reserved ranges, so the
memremap_should_map_decrypted()will return true, that is to say, the reserved memory is decrypted, then theearly_memremap_pgprot_adjust()will call thepgprot_decrypted()to clear the memory encryption mask.Quoted 7 lines
In the second kernel, because the e820 reserved ranges are not passed to the second kernel, these ranges don't sit in the e820 reserved ranges, so the the
memremap_should_map_decrypted()will return false, that is to say, the reserved memory is encrypted, and then theearly_memremap_pgprot_adjust()will also call thepgprot_encrypted()to set the memory encryption mask.Obviously, in the second kernel, the e820 reserved memory is still decrypted, it has gone wrong. So, if don't fix, kdump won't work when we use the command(kexec -s -p xxx) to load the kernel image and initramfs.
Yes, this looks better. In fact, I searched cover-letter and both patch lg, didn't find anything to tell what will happen without these patchset. We should at least tell the patch is for cleanup/improvement/fix/feature. This "if don't fix, kdump won't work ..." is the sentence I first saw telling the sequence or the problem.
Quoted 5 lines
Please do not misunderstand those questions from me with unfriendly tone, words are cold and can't express emotions exactly, and appearance. Those questions are just meaning that people may get confusion from those places.
Don't worry.
I would like to improve patch log based on your suggestion.
Regards,
Lianbo
Quoted 6 lines
What: describe the problem you met. Why: tell the root cause How: how you fix itThis is what I usually use to write patch log. Just for your reference.
Ok, thanks.
Quoted 3 lines
Thanks
Baoquan