From: Lianbo Jiang <lijiang@redhat.com> To: linux-kernel@vger.kernel.org Cc: kexec@lists.infradead.org, tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, x86@kernel.org, akpm@linux-foundation.org, bhe@redhat.com, dyoung@redhat.com, k-hagio@ab.jp.nec.com, anderson@redhat.com, linux-doc@vger.kernel.org Subject: [PATCH 2/2 v6] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Date: Thu, 10 Jan 2019 20:19:44 +0800 [thread overview] Message-ID: <20190110121944.6050-3-lijiang@redhat.com> (raw) In-Reply-To: <20190110121944.6050-1-lijiang@redhat.com> For AMD machine with SME feature, makedumpfile tools need to know whether the crashed kernel was encrypted or not. 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 sme mask to obtain the true physical address. Signed-off-by: Lianbo Jiang <lijiang@redhat.com> --- arch/x86/kernel/machine_kexec_64.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/x86/kernel/machine_kexec_64.c b/arch/x86/kernel/machine_kexec_64.c index 4c8acdfdc5a7..bc4108096b18 100644 --- a/arch/x86/kernel/machine_kexec_64.c +++ b/arch/x86/kernel/machine_kexec_64.c @@ -352,10 +352,13 @@ void machine_kexec(struct kimage *image) void arch_crash_save_vmcoreinfo(void) { + u64 sme_mask = sme_me_mask; + VMCOREINFO_NUMBER(phys_base); VMCOREINFO_SYMBOL(init_top_pgt); vmcoreinfo_append_str("NUMBER(pgtable_l5_enabled)=%d\n", pgtable_l5_enabled()); + VMCOREINFO_NUMBER(sme_mask); #ifdef CONFIG_NUMA VMCOREINFO_SYMBOL(node_data); -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Lianbo Jiang <lijiang@redhat.com> To: linux-kernel@vger.kernel.org Cc: k-hagio@ab.jp.nec.com, bhe@redhat.com, linux-doc@vger.kernel.org, x86@kernel.org, kexec@lists.infradead.org, mingo@redhat.com, bp@alien8.de, anderson@redhat.com, tglx@linutronix.de, dyoung@redhat.com, akpm@linux-foundation.org Subject: [PATCH 2/2 v6] kdump, vmcoreinfo: Export the value of sme mask to vmcoreinfo Date: Thu, 10 Jan 2019 20:19:44 +0800 [thread overview] Message-ID: <20190110121944.6050-3-lijiang@redhat.com> (raw) In-Reply-To: <20190110121944.6050-1-lijiang@redhat.com> For AMD machine with SME feature, makedumpfile tools need to know whether the crashed kernel was encrypted or not. 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 sme mask to obtain the true physical address. Signed-off-by: Lianbo Jiang <lijiang@redhat.com> --- arch/x86/kernel/machine_kexec_64.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/x86/kernel/machine_kexec_64.c b/arch/x86/kernel/machine_kexec_64.c index 4c8acdfdc5a7..bc4108096b18 100644 --- a/arch/x86/kernel/machine_kexec_64.c +++ b/arch/x86/kernel/machine_kexec_64.c @@ -352,10 +352,13 @@ void machine_kexec(struct kimage *image) void arch_crash_save_vmcoreinfo(void) { + u64 sme_mask = sme_me_mask; + VMCOREINFO_NUMBER(phys_base); VMCOREINFO_SYMBOL(init_top_pgt); vmcoreinfo_append_str("NUMBER(pgtable_l5_enabled)=%d\n", pgtable_l5_enabled()); + VMCOREINFO_NUMBER(sme_mask); #ifdef CONFIG_NUMA VMCOREINFO_SYMBOL(node_data); -- 2.17.1 _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-01-10 12:20 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-10 12:19 [PATCH 0/2 v6] kdump,vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang 2019-01-10 12:19 ` [PATCH 0/2 v6] kdump, vmcoreinfo: " Lianbo Jiang 2019-01-10 12:19 ` [PATCH 1/2 v6] kdump: add the vmcoreinfo documentation Lianbo Jiang 2019-01-10 12:19 ` Lianbo Jiang 2019-01-11 12:33 ` Borislav Petkov 2019-01-11 12:33 ` Borislav Petkov 2019-01-14 1:52 ` lijiang 2019-01-14 1:52 ` lijiang 2019-01-14 9:10 ` Borislav Petkov 2019-01-14 9:10 ` Borislav Petkov 2019-01-14 17:48 ` Kazuhito Hagio 2019-01-14 17:48 ` Kazuhito Hagio 2019-01-14 18:01 ` Borislav Petkov 2019-01-14 18:01 ` Borislav Petkov 2019-01-14 18:58 ` Dave Anderson 2019-01-14 18:58 ` Dave Anderson 2019-01-14 19:21 ` Borislav Petkov 2019-01-14 19:21 ` Borislav Petkov 2019-01-14 19:36 ` Dave Anderson 2019-01-14 19:36 ` Dave Anderson 2019-01-14 19:59 ` Borislav Petkov 2019-01-14 19:59 ` Borislav Petkov 2019-01-14 20:07 ` Dave Anderson 2019-01-14 20:07 ` Dave Anderson 2019-01-14 20:18 ` Borislav Petkov 2019-01-14 20:18 ` Borislav Petkov 2019-01-14 20:26 ` Dave Anderson 2019-01-14 20:26 ` Dave Anderson 2019-01-14 20:35 ` Borislav Petkov 2019-01-14 20:35 ` Borislav Petkov 2019-01-14 20:49 ` Dave Anderson 2019-01-14 20:49 ` Dave Anderson 2019-01-15 10:06 ` Borislav Petkov 2019-01-15 10:06 ` Borislav Petkov 2019-01-15 11:00 ` lijiang 2019-01-15 11:00 ` lijiang 2019-01-11 14:56 ` Borislav Petkov 2019-01-11 14:56 ` Borislav Petkov 2019-01-14 5:30 ` lijiang 2019-01-14 5:30 ` lijiang 2019-01-14 9:15 ` Borislav Petkov 2019-01-14 9:15 ` Borislav Petkov 2019-01-15 9:41 ` lijiang 2019-01-15 9:41 ` lijiang 2019-01-15 10:09 ` [tip:x86/kdump] kdump: Document kernel data exported in the vmcoreinfo note tip-bot for Lianbo Jiang 2019-01-10 12:19 ` Lianbo Jiang [this message] 2019-01-10 12:19 ` [PATCH 2/2 v6] kdump, vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang 2019-01-11 15:15 ` [tip:x86/kdump] x86/kdump: Export the SME " tip-bot for Lianbo Jiang
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=20190110121944.6050-3-lijiang@redhat.com \ --to=lijiang@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=anderson@redhat.com \ --cc=bhe@redhat.com \ --cc=bp@alien8.de \ --cc=dyoung@redhat.com \ --cc=k-hagio@ab.jp.nec.com \ --cc=kexec@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mingo@redhat.com \ --cc=tglx@linutronix.de \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.