Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1631920
| From | Dave Young <dyoung@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v5 31/32] x86: Add sysfs support for Secure Memory Encryption |
| Date | 2017-04-27 09:30 +0200 |
| Message-ID | <tAM2d-5H5-1@gated-at.bofh.it> (permalink) |
| References | <txTMB-1zl-13@gated-at.bofh.it> <tyOKS-2xl-9@gated-at.bofh.it> <tyOKS-2xl-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 04/21/17 at 02:55pm, Dave Hansen wrote: > On 04/18/2017 02:22 PM, Tom Lendacky wrote: > > Add sysfs support for SME so that user-space utilities (kdump, etc.) can > > determine if SME is active. > > > > A new directory will be created: > > /sys/kernel/mm/sme/ > > > > And two entries within the new directory: > > /sys/kernel/mm/sme/active > > /sys/kernel/mm/sme/encryption_mask > > Why do they care, and what will they be doing with this information? Since kdump will copy old memory but need this to know if the old memory was encrypted or not. With this sysfs file we can know the previous SME status and pass to kdump kernel as like a kernel param. Tom, have you got chance to try if it works or not? Thanks Dave
Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Re: [PATCH v5 31/32] x86: Add sysfs support for Secure Memory Encryption Dave Young <dyoung@redhat.com> - 2017-04-27 09:30 +0200
Re: [PATCH v5 31/32] x86: Add sysfs support for Secure Memory Encryption Dave Hansen <dave.hansen@intel.com> - 2017-04-27 18:00 +0200
Re: [PATCH v5 31/32] x86: Add sysfs support for Secure Memory Encryption Dave Young <dyoung@redhat.com> - 2017-04-28 07:40 +0200
csiph-web