The controls for cpu-bugs were ultimately not taken.  As the paths are
documented fully below, pick only a small subset for the example.  Include
cpupool/ as it exists now.

Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
---
CC: Juergen Gross <jgross@suse.com>
CC: Ross Lagerwall <ross.lagerwall@citrix.com>
CC: Anthony PERARD <anthony.perard@vates.tech>
CC: Michal Orzel <michal.orzel@amd.com>
CC: Jan Beulich <jbeulich@suse.com>
CC: Julien Grall <julien@xen.org>
CC: Roger Pau Monné <roger.pau@citrix.com>
CC: Stefano Stabellini <sstabellini@kernel.org>

This is mainly so the patch making eager-fpu unconditional doesn't contain a
hunk editing this file with no associated hypfs logic changes.
---
 docs/misc/hypfs-paths.pandoc | 37 +++++++-----------------------------
 1 file changed, 7 insertions(+), 30 deletions(-)

diff --git a/docs/misc/hypfs-paths.pandoc b/docs/misc/hypfs-paths.pandoc
index e86f7d0dbef9..dd089d90df53 100644
--- a/docs/misc/hypfs-paths.pandoc
+++ b/docs/misc/hypfs-paths.pandoc
@@ -89,36 +89,13 @@ the hypervisors, and in different configurations.  Specifically:
 A populated Xen hypervisor file system might look like the following example:
 
     /
-        buildinfo/           directory containing build-time data
-            config           contents of .config file used to build Xen
-        cpu-bugs/            x86: directory of cpu bug information
-            l1tf             "Vulnerable" or "Not vulnerable"
-            mds              "Vulnerable" or "Not vulnerable"
-            meltdown         "Vulnerable" or "Not vulnerable"
-            spec-store-bypass "Vulnerable" or "Not vulnerable"
-            spectre-v1       "Vulnerable" or "Not vulnerable"
-            spectre-v2       "Vulnerable" or "Not vulnerable"
-            mitigations/     directory of mitigation settings
-                bti-thunk    "N/A", "RETPOLINE", "LFENCE" or "JMP"
-                spec-ctrl    "No", "IBRS+" or "IBRS-"
-                ibpb         "No" or "Yes"
-                l1d-flush    "No" or "Yes"
-                md-clear     "No" or "VERW"
-                l1tf-barrier "No" or "Yes"
-            active-hvm/      directory for mitigations active in hvm doamins
-                msr-spec-ctrl "No" or "Yes"
-                rsb          "No" or "Yes"
-                eager-fpu    "No" or "Yes"
-                md-clear     "No" or "Yes"
-            active-pv/       directory for mitigations active in pv doamins
-                msr-spec-ctrl "No" or "Yes"
-                rsb          "No" or "Yes"
-                eager-fpu    "No" or "Yes"
-                md-clear     "No" or "Yes"
-                xpti         "No" or list of "dom0", "domU", "PCID-on"
-                l1tf-shadow  "No" or list of "dom0", "domU"
-        params/              directory with hypervisor parameter values
-                             (boot/runtime parameters)
+      buildinfo/             directory containing build-time data
+        config               contents of .config file used to build Xen
+      cpupool/               directory containing CPU Pool data
+        0/                   directory for cpupool 0
+          sched-gran         "cpu", "core" or "socket"
+      params/                directory with hypervisor parameter values
+        loglvl               "none", "error", "warning", "info", "all"
 
 ## General Paths
 
-- 
2.39.5

On 26.03.26 20:04, Andrew Cooper wrote:
> The controls for cpu-bugs were ultimately not taken.  As the paths are
> documented fully below, pick only a small subset for the example.  Include
> cpupool/ as it exists now.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Reviewed-by: Juergen Gross <jgross@suse.com>


Juergen