From: Lianbo Jiang <lijiang@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: thomas.lendacky@amd.com, bhe@redhat.com, x86@kernel.org,
kexec@lists.infradead.org, mingo@redhat.com, bp@alien8.de,
tglx@linutronix.de, dyoung@redhat.com
Subject: [PATCH 0/2 v4] add reserved e820 ranges to the kdump kernel e820 table
Date: Mon, 22 Oct 2018 15:47:05 +0800 [thread overview]
Message-ID: <20181022074707.13901-1-lijiang@redhat.com> (raw)
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.
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"
Note:
1. The patches are made based on this branch:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
2. And you need to apply the follow patch before test kdump file_load,
otherwise these patches won't work.
commit <010a93bf97c7> "resource: Fix find_next_iomem_res() iteration
issue"
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(-)
--
2.17.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2018-10-22 7:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 7:47 Lianbo Jiang [this message]
2018-10-22 7:47 ` [PATCH 1/2 v4] x86/kexec_file: add e820 entry in case e820 type string matches to io resource name Lianbo Jiang
2018-10-22 7:47 ` [PATCH 2/2 v4] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table Lianbo Jiang
2018-10-24 6:57 ` [PATCH 0/2 v4] add reserved e820 ranges to the " Dave Young
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181022074707.13901-1-lijiang@redhat.com \
--to=lijiang@redhat.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox