tast: Add swdep for whether the OS supports NMI backtrace
The Linux kernel supports NMI backtrace if either:
- We're on an x86 board
- We're on an arm64 board with a new enough kernel
Instead of saying "x86", though, we'll say non-ARM. If,
hypothetically, someone made ChromeOS support MIPS, RISC-V, PowerPC,
or whatever then we'd want to assume that the OS supports NMI
backtrace until we've made an explicit decision that it can't be
supported.
Note that on arm64 boards OS support isn't enough. We also need to
make sure that the interrupt controller supports NMI backtrace and
there aren't any firmware quirks that break NMI backtrace. That will
be detected with a corresponding hwdep.
BUG=b:197061987
TEST=./fast_build.sh -T
TEST=test against a variety of boards
Change-Id: Id0fbeb15c4eb068942354915967cffc4edced42c
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/tast/+/4998641
Tested-by: Douglas Anderson <[email protected]>
Reviewed-by: Seewai Fu <[email protected]>
Reviewed-by: Stephen Boyd <[email protected]>
Commit-Queue: Douglas Anderson <[email protected]>
diff --git a/docs/test_dependencies.md b/docs/test_dependencies.md
index d8930df..7cdf8bd 100644
--- a/docs/test_dependencies.md
+++ b/docs/test_dependencies.md
@@ -173,6 +173,7 @@
* `no_vulkan` - Build was not built with [Vulkan] enabled.
* `no_arcvm_virtio_blk_data` - Build was not built with ARCVM virtio-blk /data enabled.
* `no_gsc` - Build was not built with onboard Google security chip support.
+* `nmi_backtrace` - The Linux kernel has support for NMI backtraces.
* `nvme` - Ability to run NVMe software utilities.
* `oci` - The ability to use the `run_oci` program to execute code within
[OCI] containers.
