On 10/27/18 at 12:25am, Borislav Petkov wrote: > On Fri, Oct 26, 2018 at 06:24:40PM +0200, Petr Tesarik wrote: > > But we need the MSR value from the panic kernel environment, not while > > the production kernel is still running, right? > > Actually, we need only the encryption bit number (and it should be 0 > otherwise to denote SME wasn't enabled). > > I guess something like > > VMCOREINFO_NUMBER(sme_mask); Yes, agree. So sme_me_mask itself or the encryption bit number, both is fine. We need read and parse the memory content of crashed kernel which is mapped to /prov/vmcore by user space makedumpfile. Not only is it because user space makedumpfile can't access and get if it's sme enabled from system, we may use cp to copy /proc/vmcore to a file directly, then analyze it in another compupter. This often happen when there's something wrong with makedumpfile, we need debug makedumpfile with the complete copied file. And only telling whether sme is enabled might be not enough. Since AMD CPU might extend to support 5-level, then the current fixed bit positon 47 would need be changed. Thanks Baoquan _______________________________________________ kexec mailing list kexec@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/kexec
