From: lijiang <lijiang@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: bhe@redhat.com, x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, mingo@redhat.com, bp@alien8.de,
tglx@linutronix.de, akpm@linux-foundation.org
Subject: Re: [PATCH 2/2 v2] kdump, vmcoreinfo: Export the value of sme mask to vmcoreinfo
Date: Mon, 10 Dec 2018 11:13:35 +0800 [thread overview]
Message-ID: <685758a5-9d52-9270-e907-b4bda49a0102@redhat.com> (raw)
In-Reply-To: <20181205102407.GB6940@dhcp-128-65.nay.redhat.com>
在 2018年12月05日 18:24, Dave Young 写道:
> On 12/02/18 at 11:08am, Lianbo Jiang wrote:
>> For AMD machine with SME feature, makedumpfile tools need to know
>> whether the crash kernel was encrypted or not. If SME is enabled
>> in the first kernel, the crash kernel's page table(pgd/pud/pmd/pte)
>> contains the memory encryption mask, so need 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 | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/arch/x86/kernel/machine_kexec_64.c b/arch/x86/kernel/machine_kexec_64.c
>> index 4c8acdfdc5a7..1860fe24117d 100644
>> --- a/arch/x86/kernel/machine_kexec_64.c
>> +++ b/arch/x86/kernel/machine_kexec_64.c
>> @@ -352,10 +352,24 @@ 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());
>> + /*
>> + * Currently, the local variable 'sme_mask' stores the value of
>> + * sme_me_mask(bit 47), and also write the value of sme_mask to
>> + * the vmcoreinfo.
>> + * If need, the bit(sme_mask) might be redefined in the future,
>> + * but the 'bit63' will be reserved.
>> + * For example:
>> + * [ misc ][ enc bit ][ other misc SME info ]
>> + * 0000_0000_0000_0000_1000_0000_0000_0000_0000_0000_..._0000
>> + * 63 59 55 51 47 43 39 35 31 27 ... 3
>> + */
>> + VMCOREINFO_NUMBER(sme_mask);
>
> #define VMCOREINFO_NUMBER(name) \
> vmcoreinfo_append_str("NUMBER(%s)=%ld\n", #name, (long)name)
>
> VMCOREINFO_NUMBER is defined as above, so it looks questionable to add
> more users of that for different data types although it may work in real
> world.
>
Thank you, Dave.
For the sme_mask, the bit47 is set '1', and the VMCOREINFO_NUMBER is a signed
64 bit number(x86_64), it is big enough to the sme_mask.
> A new macro like below may be better, may need to choose a better name
> though:
> _VMCOREINFO_NUMBER(name, format, type)
> so you can pass the format specifier and data types explictly
>
That should be a good suggestion. But for now, maybe it is not time for improving it.
Because it is still big enough.
Thanks.
Lianbo
>
>>
>> #ifdef CONFIG_NUMA
>> VMCOREINFO_SYMBOL(node_data);
>> --
>> 2.17.1
>>
>
> Thanks
> Dave
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2018-12-10 3:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-02 3:08 [PATCH 0/2 v2] kdump, vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2018-12-02 3:08 ` [PATCH 1/2 v2] kdump: add the vmcoreinfo documentation Lianbo Jiang
2018-12-03 15:08 ` Borislav Petkov
2018-12-04 9:35 ` lijiang
2018-12-05 10:16 ` Dave Young
2018-12-05 14:21 ` lijiang
2018-12-05 11:30 ` Borislav Petkov
2018-12-05 14:21 ` lijiang
2018-12-05 20:29 ` Kazuhito Hagio
2018-12-10 18:32 ` Borislav Petkov
2018-12-10 21:10 ` Kazuhito Hagio
2018-12-02 3:08 ` [PATCH 2/2 v2] kdump, vmcoreinfo: Export the value of sme mask to vmcoreinfo Lianbo Jiang
2018-12-05 10:24 ` Dave Young
2018-12-10 3:13 ` lijiang [this message]
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=685758a5-9d52-9270-e907-b4bda49a0102@redhat.com \
--to=lijiang@redhat.com \
--cc=akpm@linux-foundation.org \
--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=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