From: Lianbo Jiang <lijiang@redhat.com>
To: kexec@lists.infradead.org
Cc: dyoung@redhat.com, k-hagio@ab.jp.nec.com, anderson@redhat.com,
bhe@redhat.com
Subject: [PATCH 0/2] makedumpfile needs to remove the memory encryption
Date: Tue, 22 Jan 2019 16:03:55 +0800 [thread overview]
Message-ID: <20190122080357.23381-1-lijiang@redhat.com> (raw)
The patchset did two things:
[1] add a new variable 'sme_mask' to number_table
The variable will be used to store the sme mask for crashed kernel,
the sme_mask denotes whether the old memory is encrypted or not.
[2] remove the memory encryption mask to obtain the true physical
address
For AMD machine with SME feature, if SME is enabled in the first
kernel, the crashed kernel's page table(pgd/pud/pmd/pte) contains
the memory encryption mask, so makedumpfile needs to remove the
memory encryption mask to obtain the true physical address.
References:
x86/kdump: Export the SME mask to vmcoreinfo
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=65f750e5457aef9a8085a99d613fea0430303e93
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=f263245a0ce2c4e23b89a58fa5f7dfc048e11929
Lianbo Jiang (2):
Makedumpfile: add a new variable 'sme_mask' to number_table
Remove the memory encryption mask to obtain the true physical address
arch/x86_64.c | 3 +++
makedumpfile.c | 4 ++++
makedumpfile.h | 1 +
3 files changed, 8 insertions(+)
--
2.17.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2019-01-22 8:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 8:03 Lianbo Jiang [this message]
2019-01-22 8:03 ` [PATCH 1/2] Makedumpfile: add a new variable 'sme_mask' to number_table Lianbo Jiang
2019-01-23 21:51 ` Kazuhito Hagio
2019-01-24 9:23 ` lijiang
2019-01-22 8:03 ` [PATCH 2/2] Remove the memory encryption mask to obtain the true physical address Lianbo Jiang
2019-01-23 22:16 ` Kazuhito Hagio
2019-01-24 19:33 ` Kazuhito Hagio
2019-01-25 3:17 ` lijiang
2019-01-25 3:06 ` lijiang
2019-01-25 3:55 ` dyoung
2019-01-25 14:32 ` Lendacky, Thomas
2019-01-28 1:55 ` lijiang
2019-01-28 3:15 ` lijiang
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=20190122080357.23381-1-lijiang@redhat.com \
--to=lijiang@redhat.com \
--cc=anderson@redhat.com \
--cc=bhe@redhat.com \
--cc=dyoung@redhat.com \
--cc=k-hagio@ab.jp.nec.com \
--cc=kexec@lists.infradead.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