[PATCH v2 1/2] examples: systemtap: Warn users to properly update 'amd-sev-es-vmsa.stp'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



The script references a very specific line in the kernel source code and
a very specific struct. Further changes to the kernel are likely going
to break it. Set the expectations by adding a warning to the reader.

Signed-off-by: Peter Krempa <pkrempa@xxxxxxxxxx>
---
 examples/systemtap/amd-sev-es-vmsa.stp | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/examples/systemtap/amd-sev-es-vmsa.stp b/examples/systemtap/amd-sev-es-vmsa.stp
index 551ed739b7..7bd079be71 100644
--- a/examples/systemtap/amd-sev-es-vmsa.stp
+++ b/examples/systemtap/amd-sev-es-vmsa.stp
@@ -19,6 +19,10 @@
 # A script that captures the VMSA blob for the boot vCPU and
 # first additional vCPU, when a KVM guest is booted with SEV-ES
 #
+# NOTE: This directly references specific structures and places in the
+#       kernel source code. It is expected that this example will need to be
+#       editted to match the kernel you intend to run it against.
+#
 # The captured VMSA will be printed to the console in hex format,
 # and can be converted to the required binary format by feeding
 # it through
-- 
2.39.2




[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]

  Powered by Linux