simplify README.md by foldable items

Author: louie-tsai

hardware/priority_core_turbo/README.md

@@ -14,7 +14,9 @@ Validated platforms:
 - **Intel® Xeon® 6776P**
 
 ## How PCT Works
-
+<details>
+<summary> PCT Details </summary>
+  
 PCT relies on **two Intel Speed Select features**:
 
 - **SST-TF (Turbo Frequency)**
@@ -86,9 +88,13 @@ With Hyper-Threading included, this becomes:
 ```
 
 This is the default strict bucket-0 PCT placement used by the updated set script.
+</details>
 
 ## 1. Build the Environment
 
+<details>
+<summary> Build Details </summary>
+  
 Export the kernel build variables first:
 
 ```bash
@@ -107,17 +113,28 @@ Verify `intel-speed-select` exists inside the image:
 docker compose run --rm intel-speed-select-shell 'which intel-speed-select && intel-speed-select --help | head'
 ```
 
-## 2. Check PCT Status (Read-Only)
+</details>
 
-This step verifies:
+## 2. Check PCT Status (Read-Only)
 
+<details>
+<summary> This step verifies: </summary>
+  
 - Hardware support for Intel® Speed Select features
 - SST-TF/PCT bucket-0 capacity
 - Correct package/socket-based PCT capacity counting
 - Core Power and CLOS enablement
 - Current CPU-to-CLOS mapping
 - Whether the current `TARGET_CLOS` CPU count matches the expected PCT logical CPU budget
 
+</details>
+
+Export the kernel build variables first:
+
+```bash
+source ./set_kernel_env.sh
+```
+
 Run:
 
 ```bash
@@ -126,6 +143,9 @@ docker compose --progress=plain --profile check up --abort-on-container-exit
 
 Example results when PCT and CLOS are enabled successfully:
 
+<details>
+<summary> Example results </summary>
+  
 ```bash
 ------------------------------------------------------------
 CPU and Intel Speed Select Capability
@@ -196,6 +216,8 @@ Summary
 Done.
 ```
 
+</details>
+
 The check script writes the current target-CLOS CPU list to:
 
 ```text
@@ -205,10 +227,6 @@ The check script writes the current target-CLOS CPU list to:
 For the example above, `clos0_cpulist.txt` contains 32 logical CPUs. With
 Hyper-Threading enabled, that corresponds to 16 physical PCT cores.
 
-> **Note:** CLOS assignment and CLOS enforcement are different. `get-assoc` may
-> show CPU-to-CLOS mappings even when `core-power info` reports Core Power or
-> CLOS disabled. For PCT benchmarking, ensure both Core Power and CLOS are enabled.
-
 ## 3. Set PCT (Dispatch Package-Level PCT Cores Across Powerdomain Anchors)
 
 This step **activates PCT in practice** by assigning selected HP CPUs to **CLOS0**.
@@ -224,8 +242,9 @@ CPUs in CLOS0.
 
 ### Set-script behavior
 
-The setup script performs the following actions:
-
+<details>
+<summary> The setup script performs the following actions: </summary>
+  
 - Detects PCT capacity from `intel-speed-select turbo-freq info -l <TDP_LEVEL>`.
 - Counts `bucket-0` once per package/socket.
 - Derives `HP_PER_PACKAGE` from `PCT_CORES_PER_PACKAGE` unless overridden.
@@ -237,6 +256,14 @@ The setup script performs the following actions:
     - **Selected HP CPUs → CLOS0** by default
     - **All remaining CPUs → CLOS2** by default
 
+</details>
+
+Export the kernel build variables first:
+
+```bash
+source ./set_kernel_env.sh
+```
+
 Run the setup:
 
 ```bash
@@ -251,8 +278,9 @@ DRY_RUN=1 docker compose --progress=plain --profile set up --abort-on-container-
 
 ### Example: package capacity dispatched across reporting powerdomain anchors
 
-Latest validated output:
-
+<details>
+<summary> Example results </summary>
+  
 ```bash
 intel-speed-select-set-1  | ------------------------------------------------------------
 intel-speed-select-set-1  | PCT capacity from SST-TF bucket-0
@@ -324,12 +352,9 @@ intel-speed-select-set-1  |
 intel-speed-select-set-1  | Done.
 ```
 
-After applying the set flow, run the check flow again:
-
-```bash
-docker compose --progress=plain --profile check up --abort-on-container-exit
-```
+</details>
 
+After applying the set flow, run the check flow again.
 The check output should show:
 
 ```text
@@ -346,6 +371,9 @@ the frequency benchmark can access host CPU frequency interfaces directly.
 
 ### Prerequisites
 
+<details>
+<summary> Details </summary>
+  
 The host benchmark script reads the CPU list generated by the check profile:
 
 ```bash
@@ -370,6 +398,8 @@ which perfspect
 perfspect --help | head
 ```
 
+</details>
+
 ### Run the benchmark
 
 Run the full flow:
@@ -381,6 +411,9 @@ docker compose --progress=plain --profile check up --abort-on-container-exit
 ./run_host_perfspect_benchmark.sh
 ```
 
+<details>
+<summary> Details </summary>
+
 Default host benchmark command:
 
 ```bash
@@ -393,6 +426,7 @@ Override the PerfSpect benchmark options with `PERFSPECT_ARGS`:
 PERFSPECT_ARGS="--speed --frequency --memory --no-summary" \
 ./run_host_perfspect_benchmark.sh
 ```
+</details>
 
 ### Analyze results
 
@@ -418,6 +452,9 @@ frequency, and frequency gradually steps down as more physical cores become acti
 
 ## 5. Debug / Manual Inspection (Optional)
 
+<details>
+<summary> Debug Details </summary>
+
 This section is useful for **troubleshooting**, **validation**, or **manual experimentation**
 with Intel® Speed Select and PCT behavior.
 
@@ -435,3 +472,4 @@ intel-speed-select turbo-freq info -l 1
 intel-speed-select core-power info
 intel-speed-select -c 0 core-power get-assoc
 ```
+</details>