Merge pull request #2840 from madeline-underwood/kernel

Kernel_reviewed

Author: jasonrandrews

content/learning-paths/servers-and-cloud-computing/kernel-build/_index.md

@@ -1,10 +1,6 @@
 ---
 title: Build Linux kernels for Arm cloud instances
 
-draft: true
-cascade:
-    draft: true
-
 minutes_to_complete: 60
 
 who_is_this_for: This is an advanced topic for software developers building custom Linux kernels on Arm servers and cloud instances.

content/learning-paths/servers-and-cloud-computing/kernel-build/_next-steps.md

@@ -4,26 +4,7 @@ next_step_guidance: >
     
 recommended_path: "/learning-paths/servers-and-cloud-computing/profiling-for-neoverse/"
 
-further_reading:
-    - resource:
-        title: TuxMake documentation
-        link: https://tuxmake.org/
-        type: documentation
-    - resource:
-        title: Linux kernel documentation
-        link: https://www.kernel.org/doc/html/latest/
-        type: documentation
-    - resource:
-        title: arm_kernel_install_guide repository
-        link: https://github.com/geremyCohen/arm_kernel_install_guide
-        type: website
-    - resource:
-        title: Arm Neoverse system architecture
-        link: https://developer.arm.com/documentation/den0024/latest/
-        type: documentation
-
-
-### FIXED, DO NOT MODIFY THIS FILE, unless you need to update the 'further_reading' list.
+### FIXED, DO NOT MODIFY THIS FILE.
 weight: 21
 layout: learningpathall
 ---

content/learning-paths/servers-and-cloud-computing/kernel-build/how-to-1.md

@@ -44,8 +44,8 @@ The repository you just cloned contains helper scripts for building and managing
 
 The `kernel_build_and_install.sh` script supports two main workflows:
 
-1. **General usage** - Build kernels for direct installation or downstream packaging
-2. **Fastpath usage** - Build kernels with additional headers and perf configuration needed by the Fastpath validation tool
+-  **General usage** - Build kernels for direct installation or downstream packaging
+- **Fastpath usage** - Build kernels with additional headers and perf configuration needed by the Fastpath validation tool
 
 ### About Fastpath
 
@@ -90,6 +90,29 @@ Check that the script is executable and displays help information:
 ./scripts/kernel_build_and_install.sh --help
 ```
 
-The expected output shows all available flags and usage examples.
+The expected output is similar to:
+
+```output
+Usage: kernel_build_and_install.sh [OPTIONS]
+
+Options:
+  --demo-default-build          Build v6.18.1 with default configuration
+  --demo-fastpath-build         Build v6.18.1 and v6.19-rc1 with Fastpath configs
+  --tag <tag>                   Specify a kernel version to build
+  --tags <tag1,tag2,...>        Build multiple kernel versions in parallel
+  --kernel-install [true|false|tag]  Install kernel after building
+  --fastpath [true|false]       Enable Fastpath configuration overlay
+  --change-to-64k [true|false]  Build kernel with 64 KB page size
+  --help                        Display this help message
+...
+```
+
+## What you've accomplished and what's next
+
+In this section, you've:
+- Configured an Arm cloud instance with the required build dependencies
+- Cloned the kernel build helper repository
+- Learned about the available build script flags for general and Fastpath workflows
+- Verified your build environment is ready
 
-You're now ready to build Linux kernels on your Arm instance. The next section covers standard kernel build workflows.
+The next section covers standard kernel build workflows for direct installation or downstream packaging.

content/learning-paths/servers-and-cloud-computing/kernel-build/how-to-2.md

@@ -6,16 +6,16 @@ weight: 3
 layout: learningpathall
 ---
 
-This section covers standard kernel build workflows for direct installation or downstream packaging.
-
+## Standard kernel workflows
 
+Standard kernel builds produce general-purpose kernels suitable for production deployment, development testing, or distribution packaging. These workflows let you build specific versions, install them directly, or package them for later use.
 
-## Kernel Build only
+This section covers standard kernel build workflows for direct installation or downstream packaging.
 
-{{% notice Note %}}
-The kernel versions given in the \--tags flag, such as `v6.18.1` in the first example below, are arbitrary (but valid) Linux kernel versions; If you prefer to use kernel versions different from the examples, its ok to replace it with your alternative.
+{{% notice Note on kernel build only %}}
+The kernel versions given in the \--tags flag, such as `v6.18.1` in the first example below, are arbitrary (but valid) Linux kernel versions. If you prefer to use kernel versions different from the examples, you can replace them with your preferred versions.
 
-Kernel.org hosts all official Linux kernel releases: https://www.kernel.org/.  Feel free to browse and select any stable or mainline release version depicted.
+Kernel.org hosts all official Linux kernel releases: https://www.kernel.org/. Browse and select any stable or mainline release version.
 {{% /notice %}}
 
 
@@ -65,13 +65,15 @@ This command writes a self-contained plan such as `/tmp/kernel_plan_v6.18.1_<has
   --dry-run
 ```
 
-Run the plan file later—on the same host or another system with the required dependencies—to replay the exact workflow:
+Run the plan file later—on the same host or another system with the required dependencies—to replay the exact workflow. Replace `<hash>` with the actual hash value from your generated plan file:
 
 ```bash
 bash /tmp/kernel_plan_v6.18.1_<hash>.sh
 ```
 
-## Kernel Install
+You can use tab completion or `ls /tmp/kernel_plan_*.sh` to find the exact filename.
+
+## Install kernel
 
 {{% notice Note %}}
 The following sections demonstrate build and install scenarios.  
@@ -117,7 +119,7 @@ This approach is useful when you want to:
 - Compare different kernel versions
 - Prepare multiple kernels for testing
 - Build a library of kernel versions for deployment
-- 
+
 To build two kernel versions in parallel, run the following command (it will build both `v6.18.1` and `v6.19-rc1`, but only install `v6.18.1`):
 
 ```bash
@@ -156,7 +158,7 @@ The expected output is `65536` for 64 KB builds, compared to `4096` for standard
 
 ### Install previously built kernels
 
-As there are two input formats for building kernel artifacts which match the build output formats: flat files and Debian packages.  Choose the appropriate installation method based on your prior build format.
+There are two input formats for kernel artifacts that match the build output formats: flat files and Debian packages. Choose the appropriate installation method based on your prior build format.
 
 #### Flat-file installation
 
@@ -183,7 +185,7 @@ To install from previously built Debian packages (`.deb` files):
 
 This installs the `.deb` artifacts produced earlier via `--include-bindeb-pkg`, expecting files such as `linux-image-*` and `linux-headers-*` to exist in the source directory.
 
-### What you've accomplished and what's next
+## What you've accomplished and what's next
 
 In this section, you've learned how to:
 - Build standard Linux kernels for Arm instances

content/learning-paths/servers-and-cloud-computing/kernel-build/how-to-3.md

@@ -5,6 +5,7 @@ weight: 4
 ### FIXED, DO NOT MODIFY
 layout: learningpathall
 ---
+## What is Fastpath mode?
 
 Fastpath builds use the same TuxMake pipelines but add a configuration fragment that exposes the interfaces needed by the Fastpath testing framework. This includes extra headers, Linux Perf for performance profiling, and Docker so Fastpath can control and automate testing.
 
@@ -13,9 +14,9 @@ Fastpath builds use the same TuxMake pipelines but add a configuration fragment
 Fastpath workflows are build-only: don't combine `--fastpath true` (or the demo shortcut) with `--kernel-install` or any `--install-from` commands. 
 
 The proper workflow is:
-1. Build the kernel with Fastpath configuration enabled
-2. Copy the flat artifacts (`Image.gz`, `modules.tar.xz`, and `config`) to the Fastpath host
-3. Let the Fastpath tooling handle deployment to the SUT (System Under Test)
+- Build the kernel with Fastpath configuration enabled
+- Copy the flat artifacts (`Image.gz`, `modules.tar.xz`, and `config`) to the Fastpath host
+- Let the Fastpath tooling handle deployment to the SUT (System Under Test)
 
 ### Install Docker for Fastpath