Hello Martin, Thanks for your contribution. Your emails contain a footer that threatens with legal repercussions if their contents are treated in a certain way. This usually means that, even if some people may comment on the code, there is no way we can legally merge it, given that these restrictions are incompatible with the GPL So please find a way to resend these emails without the footers. I'll be happy to look into more detail once you do that. -- Ard. On Fri, 10 Sept 2021 at 23:34, Martin Fernandez <martin.fernandez@xxxxxxxxxxxxx> wrote: > > Show the value of EFI_MEMORY_CPU_CRYPTO of the system memory as a whole > on each memory node in sysfs. > > This is a first step in a serie of patches for exporting the needed > information to userspace to determine if a machine is doing using > Intel's TME or MKTME. > > In a next patch I'm going to export if TME/MKTME is activated by the > BIOS to sysfs, since right now for the user, this information is only > available in the kernel logs, and it's not appropiate for fwupd to scan > the boot logs just to parse an integer. I'm looking for suggestions > for where to store this value. > > Martin Fernandez (1): > x86: Export information about hardware memory encryption to sysfs > > Documentation/ABI/testing/sysfs-devices-node | 11 +++ > arch/x86/include/asm/numa.h | 2 + > arch/x86/mm/numa.c | 5 ++ > arch/x86/mm/numa_emulation.c | 2 +- > arch/x86/platform/efi/efi.c | 27 +++++++ > drivers/base/node.c | 80 +++++++++++++++++++- > include/linux/efi.h | 7 ++ > include/linux/node.h | 5 ++ > 8 files changed, 137 insertions(+), 2 deletions(-) > create mode 100644 Documentation/ABI/testing/sysfs-devices-node > > > base-commit: 0bcfe68b876748762557797a940d0a82de700629 > -- > 2.30.2 > > -- > > > This e-mail and any attachments may contain information that is > privileged, confidential, and/or exempt from disclosure under applicable > law. If you are not the intended recipient, you are hereby notified that > any disclosure, copying, distribution or use of any information contained > herein is strictly prohibited. If you have received this transmission in > error, please immediately notify the sender and destroy the original > transmission and any attachments, whether in electronic or hard copy > format, without reading or saving. > > > > > > > > > > > >
