| commit | 268c1096a7fc7f11d31fdf8aacc4c0276b3caed5 | [log] [tgz] |
|---|---|---|
| author | Raghul Rajakumar <rrajakumar@nvidia.com> | Wed Nov 12 19:49:27 2025 +0530 |
| committer | Raghul Rajakumar <rrajakumar@nvidia.com> | Tue Dec 16 04:36:58 2025 -0800 |
| tree | f1b45056ff9102a9b7e524e89e514e2a1454ae9d | |
| parent | 5762211858d93a68a96ead990c73d4a88eaf783f [diff] |
Adding update shmem support for power smoothing V2 properties fixes jira https://jirasw.nvidia.com/browse/DGXOPENBMC-21509 Signed-off-by: Raghul Rajakumar <rrajakumar@nvidia.com>
sudo apt install build-essential gcc-13 g++-13 python3-dev nlohmann-json3-dev pip install --user meson ninja
sudo apt install libboost1.83-all-dev # for Ubuntu 22.04
or
sudo apt install libboost1.84-all-dev # for Ubuntu 24.04
or if it not installed, download and install it from source.
wget https://downloads.sourceforge.net/project/boost/boost/1.84.0/boost_1_84_0.tar.gz tar -xzf boost_1_84_0.tar.gz cd boost_1_84_0 ./bootstrap.sh --prefix=/usr/local ./b2 install
git archive --remote=ssh://git@gitlab-master.nvidia.com:12051/dgx/bmc/libmctp.git develop libmctp-externals.h | tar -x -C common/
# Configure Meson build with debug options and compiler flags (copied from openbmc-build-scripts repo) meson setup --reconfigure -Db_sanitize=address,undefined -Db_lundef=true -Dwerror=true -Dwarning_level=3 -Db_colorout=never -Ddebug=true -Doptimization=g -Dcpp_args="-DBOOST_USE_VALGRIND -Wno-error=invalid-constexpr -Wno-invalid-constexpr -Werror=uninitialized -Wno-error=maybe-uninitialized -Werror=strict-aliasing" builddir # Build all targets ninja -C builddir
# Run all unit tests meson test -C builddir # Run specific unit test meson test -C builddir nsmChassis_test
If you encounter sdbusplus build errors, verify that the revision in subprojects/sdbusplus.wrap matches the version specified in the openbmc-build-scripts repository. Version mismatches can cause build failures.
For other subproject-related errors, you can update all subproject repositories to their latest commits using:
cd subprojects
find -L . -type d -name ".git" | while read gitdir; do
repo=$(dirname "$gitdir")
echo "Pulling updates in $repo"
cd "$repo"
git pull
cd - > /dev/null
done
# Debug all tests meson test -C builddir --gdb # Debug specific test meson test -C builddir nsmChassis_test --gdb
{ "version": "0.2.0", "configurations": [ { "name": "Debug file with Meson", "type": "cppdbg", "request": "launch", "program": "${workspaceFolder}/builddir/${relativeFileDirname}/${fileBasenameNoExtension}", "cwd": "${workspaceFolder}/builddir/${relativeFileDirname}", "preLaunchTask": "Compile meson test" } ] }
{ "version": "2.0.0", "tasks": [ { "label": "Compile meson test", "type": "shell", "command": "meson compile -C builddir ${fileBasenameNoExtension}", "group": "build", } ] }
To ensure code consistency and formatting standards in the CI pipeline, clang-format-19 needs to be installed. Follow the steps below to install clang-format-19 on your system:
# Update the package list sudo apt update # Install clang-format-19 sudo apt install clang-format-19
This will install clang-format-19 on your system, enabling it for use in the CI pipeline.
To automatically format your code before each commit, create a pre-commit hook with the following steps:
cat > .git/hooks/pre-commit << EOL
#!/bin/sh
# Get list of staged files that are C/C++ source files
files=$(git diff --cached --name-only --diff-filter=ACMR | grep ".*\.[ch]\(pp\)\?$")
if [ -n "$files" ]; then
# Format the files
clang-format-19 -i $files
# Add the formatted files back to staging
git add $files
# Check if any files were modified after formatting
if ! git diff --cached --quiet; then
echo "Formatted C/C++ files were automatically fixed up"
fi
fi
exit 0
EOL
chmod +x .git/hooks/pre-commit
The NSM daemon tracks various sensor polling operations using progress counters. These counters are stored in a memory-mapped file descriptor (memfd) and can be accessed via D-Bus for duming, monitoring and debugging purposes.
Each counter type tracks a specific aspect of sensor polling operations:
sensorManager.cpp::pollPrioritySensors()nsmGpmOemFactory.cpp when creating GPM sensorssensorManager.cpp::updateLongRunningSensor()sensorManager.cpp::pollNonPrioritySensors() when pollingType == StaticsensorManager.cpp::pollNonPrioritySensors() when pollingType == RoundRobinSENSOR_POLLING_TIME (typically 150ms)sensorManager.cpp::pollPrioritySensors() when (t1 - t0) > pollingTimeInUsecnsmDevice.cpp::postPatchIO()nsmEvent.cpp::DelegatingEventHandler::delegate()NSM_SUCCESS or NSM_SW_ERROR_TIMEOUTprogressCounters.cpp::increment() when rc != NSM_SUCCESS and rc != NSM_SW_ERROR_TIMEOUTNSM_SW_ERROR_TIMEOUT)progressCounters.cpp::increment() when rc == NSM_SW_ERROR_TIMEOUTProgress counters can be configured via meson options:
progressCounter: Enable/disable progress counter functionality (default: enabled)sensor-progress-counters-dump-count-threshold: Number of counter updates before dumping to memfd (default: 100000)sensor-progress-counters-dump-time-threshold: Time threshold in microseconds before dumping (default: 600000000 = 10 minutes)sensor-progress-counters-memfd-size: Size of the memory-mapped file in bytes (default: 65536)Counter data is exposed via D-Bus at:
/xyz/openbmc_project/progress_counters/<device_eid>
Use the nsmProgressCountersReader tool to read counter data:
# Read counters for all devices nsmProgressCountersReader # Read counters for specific device nsmProgressCountersReader <device_eid>
To add a new progress counter type, follow these steps:
Add your new counter type to nsmd/nsmProgressCounters/progressCounterType.hpp:
enum class ProgressCounterType { Priority, GpuPerformanceMonitoring, // ... existing counters ... YourNewCounter, // Add here, before EnumCount (must be last) EnumCount, };
Important: Always add new counters before EnumCount, as EnumCount must remain the last entry for the CountersCount calculation.
Add comprehensive documentation for your new counter in the nsmd/nsmProgressCounters/progressCounterType.hpp file:
/** * @brief Your new counter description * * Incremented when: Describe when this counter is incremented * * Location: File.cpp::functionName() */ YourNewCounter,
Add your new counter to the “Counter Types and When They Are Incremented” section in this README with:
Add your counter name to the counterNames array in nsmd/nsmProgressCounters/progressCounterReader.cpp:
static constexpr std::array<std::string_view, CountersCount> counterNames = { "Priority", "GPM", "LongRunning", "Static", "RoundRobin", "PriorityTimeExceeded", "PostPatch", "Event", "Error", "Timeout", "YourNewCounter", // Add your counter name here };
Important: The order must match the enum order in ProgressCounterType. This array is used by nsmProgressCountersReader to display counter names in CSV output.
In the appropriate location in your code, increment the counter:
// For successful operations nsmDevice->progressCounters.increment(ProgressCounterType::YourNewCounter, rc, timestamp); // Or directly without return code checking nsmDevice->progressCounters.increment(ProgressCounterType::YourNewCounter, timestamp);
Counters are stored in a packed structure for efficient memory usage:
struct __attribute__((packed)) CounterDataRow { uint32_t key; // Iteration/dump key uint64_t timestamp; // Timestamp in microseconds CountersArray counters; // Array of counter values };
The data rotates in the memfd using key % maxRows to ensure bounded memory usage.
Successful build should generate three binary artifacts.
A Daemon that can discover NSM endpoint, gather telemetry data from the endpoints, and can publish them to D-Bus or similar IPC services, for consumer services like bmcweb.
nsmtool is a client tool that acts as a NSM requester which can be invoked from the BMC. nsmtool sends the request message and parse the response message & display it in readable format.
A mockup NSM responder that can be used for development purpose. Its primary usage is to test nsmd and nsmtool features on an emulator like QEMU.
Follow this steps to run nsmMockupResponder: Step 1 - On the QEMU instance, restart the nsmd service.
Step 2 Assign an address to the loopback (lo) interface $ mctp addr add 12 dev lo
Step 3 Immediately start the mock responder using the assigned address $ nsmMockupResponder -v -d Baseboard -i 0 -e 12
Run Step 3 right after Step 2. If there is any delay, nsmd will fail to detect the endpoint. If detection fails, repeat all steps from the beginning.