commit | 337a0978efd615ef27ff1ba8241974a7c020d845 | [log] [tgz] |
---|---|---|
author | Zev Weiss <zev@bewilderbeest.net> | Fri Mar 08 08:31:15 2024 +0000 |
committer | Vernon Mauery <vernon.mauery@linux.intel.com> | Wed Apr 10 22:08:30 2024 +0000 |
tree | 70000a7c4611d8412d217455ddb8dec88191e324 | |
parent | 04b0b0799e8417c37024fc24787c2a9f28d8c0de [diff] |
chassis: Switch NMI handling to Control.Host.NMI interface Nothing in mainline OpenBMC appears to implement a service for the Chassis.Control.NMISource interface as far as I can tell, so 'ipmitool chassis power diag' had no way of working. With this change we switch ipmid to use the same interface that bmcweb uses to handle a POST of '{"ResetType":"Nmi"}' to the ComputerSystem.Reset endpoint (which x86-power-control implements and thus actually works). Tested: 'ipmitool chassis power diag' now successfully triggers an NMI on the host via x86-power-control instead of simply logging an error on the BMC. Signed-off-by: Zev Weiss <zev@bewilderbeest.net> Change-Id: Ic4c6cb2546cbd3877953fac9dd04ea752810c46c
meson builddir ninja -C builddir
meson builddir -Dbuildtype=minsize -Db_lto=true -Dtests=disabled ninja -C builddir
If any of the dependencies are not found on the host system during configuration, meson automatically gets them via its wrap dependencies mentioned in ipmid/subprojects
.
meson builddir -Dwrap_mode=nofallback ninja -C builddir
meson builddir -Dbuildtype=debug ninja -C builddir
meson builddir -Db_coverage=true -Dtests=enabled ninja -C builddir test ninja -C builddir coverage