You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
62 lines
2.5 KiB
62 lines
2.5 KiB
2 years ago
|
From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
|
||
|
|
From: Javier Martinez Canillas <javierm@redhat.com>
|
||
|
|
Date: Sat, 7 Nov 2020 01:03:18 +0100
|
||
|
|
Subject: [PATCH] docs: Document the cutmem command
|
||
|
|
|
||
|
|
The command is not present in the docs/grub.texi user documentation.
|
||
|
|
|
||
|
|
Reported-by: Daniel Kiper <daniel.kiper@oracle.com>
|
||
|
|
Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
|
||
|
|
Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
|
||
|
|
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
|
||
|
|
---
|
||
|
|
docs/grub.texi | 21 +++++++++++++++++++++
|
||
|
|
1 file changed, 21 insertions(+)
|
||
|
|
|
||
|
|
diff --git a/docs/grub.texi b/docs/grub.texi
|
||
|
|
index c55452307..314bbeb84 100644
|
||
|
|
--- a/docs/grub.texi
|
||
|
|
+++ b/docs/grub.texi
|
||
|
|
@@ -3942,6 +3942,7 @@ you forget a command, you can run the command @command{help}
|
||
|
|
* cpuid:: Check for CPU features
|
||
|
|
* crc:: Compute or check CRC32 checksums
|
||
|
|
* cryptomount:: Mount a crypto device
|
||
|
|
+* cutmem:: Remove memory regions
|
||
|
|
* date:: Display or set current date and time
|
||
|
|
* devicetree:: Load a device tree blob
|
||
|
|
* distrust:: Remove a pubkey from trusted keys
|
||
|
|
@@ -4103,6 +4104,8 @@ this page is to be filtered. This syntax makes it easy to represent patterns
|
||
|
|
that are often result of memory damage, due to physical distribution of memory
|
||
|
|
cells.
|
||
|
|
|
||
|
|
+The command is similar to @command{cutmem} command.
|
||
|
|
+
|
||
|
|
Note: The command is not allowed when lockdown is enforced (@pxref{Lockdown}).
|
||
|
|
This prevents removing EFI memory regions to potentially subvert the
|
||
|
|
security mechanisms provided by the UEFI secure boot.
|
||
|
|
@@ -4266,6 +4269,24 @@ GRUB suports devices encrypted using LUKS and geli. Note that necessary modules
|
||
|
|
be used.
|
||
|
|
@end deffn
|
||
|
|
|
||
|
|
+@node cutmem
|
||
|
|
+@subsection cutmem
|
||
|
|
+
|
||
|
|
+@deffn Command cutmem from[K|M|G] to[K|M|G]
|
||
|
|
+Remove any memory regions in specified range.
|
||
|
|
+@end deffn
|
||
|
|
+
|
||
|
|
+This command notifies the memory manager that specified regions of RAM ought to
|
||
|
|
+be filtered out. This remains in effect after a payload kernel has been loaded
|
||
|
|
+by GRUB, as long as the loaded kernel obtains its memory map from GRUB. Kernels
|
||
|
|
+that support this include Linux, GNU Mach, the kernel of FreeBSD and Multiboot
|
||
|
|
+kernels in general.
|
||
|
|
+
|
||
|
|
+The command is similar to @command{badram} command.
|
||
|
|
+
|
||
|
|
+Note: The command is not allowed when lockdown is enforced (@pxref{Lockdown}).
|
||
|
|
+ This prevents removing EFI memory regions to potentially subvert the
|
||
|
|
+ security mechanisms provided by the UEFI secure boot.
|
||
|
|
|
||
|
|
@node date
|
||
|
|
@subsection date
|