Inter-revision diff: cover letter

Comparing v2 (message) to v1 (message)

--- v2
+++ v1
@@ -1,46 +1,55 @@
-Show for each NUMA node the value of EFI_MEMORY_CPU_CRYPTO in its
-memory.
+Show the value of EFI_MEMORY_CPU_CRYPTO of the system memory as a whole
+on each memory node in sysfs.
 
-This is a serie of patches for exporting the needed information to
-userspace to determine if a machine is using Intel's TME or MKTME.
+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 appropriate for fwupd to
-scan the boot logs just to parse an integer. I'm looking for
-suggestions for where to store this value.
+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.
 
-Changelog v2:
+Martin Fernandez (1):
+  x86: Export information about hardware memory encryption to sysfs
 
-The value shown in each node now only corresponds to memory in that
-node in particular
-
-Martin Fernandez (5):
-  Extend memblock to support memory encryption
-  Extend pg_data_t to hold information about memory encryption
-  Extend e820_table to hold information about memory encryption
-  Mark e820_entries as crypto capable from EFI memmap
-  Show in sysfs if a memory node is able to do memory encryption
-
- Documentation/ABI/testing/sysfs-devices-node |  12 +++
- arch/x86/include/asm/e820/api.h              |   2 +
- arch/x86/include/asm/e820/types.h            |   1 +
- arch/x86/include/asm/numa.h                  |   7 ++
- arch/x86/kernel/e820.c                       |  32 +++++-
- arch/x86/mm/numa.c                           |   5 +
- arch/x86/mm/numa_emulation.c                 |   2 +-
- arch/x86/platform/efi/efi.c                  | 108 +++++++++++++++++++
- drivers/base/node.c                          |  72 ++++++++++++-
- include/linux/memblock.h                     |   6 ++
- include/linux/mmzone.h                       |   2 +
- include/linux/node.h                         |   1 +
- mm/memblock.c                                |  74 +++++++++++++
- mm/page_alloc.c                              |   1 +
- 14 files changed, 321 insertions(+), 4 deletions(-)
+ 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: 3906fe9bb7f1a2c8667ae54e967dc8690824f4ea
+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.
+
+
+
+
+
+
+
+
+
+
+
+
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help