Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1590136
| From | Dave Young <dyoung@redhat.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME |
| Date | 2017-03-01 10:40 +0100 |
| Message-ID | <tg8TL-179-15@gated-at.bofh.it> (permalink) |
| References | <tbyvy-1iO-79@gated-at.bofh.it> <tbT6V-6aX-5@gated-at.bofh.it> <tbT6V-6aX-3@gated-at.bofh.it> <tg8TL-179-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Hi Tom, On 02/17/17 at 10:43am, Tom Lendacky wrote: > On 2/17/2017 9:57 AM, Konrad Rzeszutek Wilk wrote: > > On Thu, Feb 16, 2017 at 09:47:55AM -0600, Tom Lendacky wrote: > > > Provide support so that kexec can be used to boot a kernel when SME is > > > enabled. > > > > Is the point of kexec and kdump to ehh, dump memory ? But if the > > rest of the memory is encrypted you won't get much, will you? > > Kexec can be used to reboot a system without going back through BIOS. > So you can use kexec without using kdump. > > For kdump, just taking a quick look, the option to enable memory > encryption can be provided on the crash kernel command line and then Is there a simple way to get the SME status? Probably add some sysfs file for this purpose. > crash kernel can would be able to copy the memory decrypted if the > pagetable is set up properly. It looks like currently ioremap_cache() > is used to map the old memory page. That might be able to be changed > to a memremap() so that the encryption bit is set in the mapping. That > will mean that memory that is not marked encrypted (EFI tables, swiotlb > memory, etc) would not be read correctly. Manage to store info about those ranges which are not encrypted so that memremap can handle them? > > > > > Would it make sense to include some printk to the user if they > > are setting up kdump that they won't get anything out of it? > > Probably a good idea to add something like that. It will break kdump functionality, it should be fixed instead of just adding printk to warn user.. Thanks Dave
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> - 2017-02-17 17:00 +0100
Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME Dave Young <dyoung@redhat.com> - 2017-03-01 10:40 +0100
Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME Dave Young <dyoung@redhat.com> - 2017-03-01 11:00 +0100
Re: [RFC PATCH v4 26/28] x86: Allow kexec to be used with SME Dave Young <dyoung@redhat.com> - 2017-03-08 09:20 +0100
csiph-web