@@ -153,6 +153,16 @@ function set_user_data() {
echo "${USERDATA_VALUE}" > "${VALUE_PATH}"
}
+function set_cpu_nr() {
+ if [[ ! -f "${NETCONS_PATH}""/userdata/populate_cpu_nr" ]]
+ then
+ echo "Populate CPU configfs path not available in ${NETCONS_PATH}/userdata/populate_cpu_nr" >&2
+ exit "${ksft_skip}"
+ fi
+
+ echo 1 > "${NETCONS_PATH}""/userdata/populate_cpu_nr"
+}
+
function listen_port_and_save_to() {
local OUTPUT=${1}
# Just wait for 2 seconds
@@ -185,6 +195,12 @@ function validate_result() {
exit "${ksft_fail}"
fi
+ if ! grep -q "cpu=[0-9]\+" "${TMPFILENAME}"; then
+ echo "FAIL: 'cpu=' not found in ${TMPFILENAME}" >&2
+ cat "${TMPFILENAME}" >&2
+ exit "${ksft_fail}"
+ fi
+
# Delete the file once it is validated, otherwise keep it
# for debugging purposes
rm "${TMPFILENAME}"
@@ -254,6 +270,8 @@ set_network
create_dynamic_target
# Set userdata "key" with the "value" value
set_user_data
+# Auto populate CPU number
+set_cpu_nr
# Listed for netconsole port inside the namespace and destination interface
listen_port_and_save_to "${OUTPUT_FILE}" &
# Wait for socat to start and listen to the port.
Expand the existing netconsole selftest to verify the functionality of the recently added CPU number auto-population feature in the netconsole userdata. The changes include enabling the "populate_cpu_nr" option on the netconsole target before sending the test data, and validating that the received data on the listener side contains a "cpu=" entry in the userdata, indicating that the CPU number was successfully auto-populated. This addition to the netconsole selftest ensures that the new CPU number auto-population feature works as expected and helps catch any regressions in this functionality. Signed-off-by: Breno Leitao <leitao@debian.org> --- tools/testing/selftests/drivers/net/netcons_basic.sh | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)