| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 26 Oct 2018 18:24:40 +0200
From: Petr Tesarik <ptesarik@...e.cz>
To: lijiang <lijiang@...hat.com>
Cc: Boris Petkov <bp@...en8.de>, linux-kernel@...r.kernel.org,
bhe@...hat.com, x86@...nel.org, kexec@...ts.infradead.org,
mingo@...hat.com, tglx@...utronix.de, dyoung@...hat.com
Subject: Re: [PATCH] kdump, vmcoreinfo: Export sme_me_mask value to
vmcoreinfo
On Fri, 26 Oct 2018 20:32:11 +0800
lijiang <lijiang@...hat.com> wrote:
>[...]
> For AMD machine with the SME feature, the msr 'MSR_K8_SYSCFG' can examine
> whether SME is enabled in kernel, but the kexec is also userspace tool,
> it has no permission to access the msr.
But we need the MSR value from the panic kernel environment, not while
the production kernel is still running, right?
If so, then this reminds me that I have wanted for a long time to store
more of the hardware state in a vmcore NOTE after a kernel crash ...
control registers, MSRs and whatnot. Of course, this would be a
long-term project, but I wonder what other people think about it in
general.
Just my 2 cents,
Petr T
> Furthermore, i also tried to read the "/dev/cpu/cpu[number]/msr", but
> the value depends on BIOS's configuration. That is to say, if SME is
> set in BIOS, the value of msr is always 0xF40000 whatever the kernel
> commandline parameter is "mem_encrypt=on" or "mem_encrypt=off".
>
> If i made a mistake, please help to point it out.
>
> Thanks.
> Lianbo
>
> _______________________________________________
> kexec mailing list
> kexec@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
Powered by blists - more mailing lists