diff options
| author | Leon Romanovsky <leonro@nvidia.com> | 2026-07-16 04:20:30 -0400 |
|---|---|---|
| committer | Leon Romanovsky <leon@kernel.org> | 2026-07-20 09:00:40 -0400 |
| commit | fbf03a08679ea02764f25f26564252e879cf14a4 (patch) | |
| tree | d4e06dd8764215052c9bb6344ca724c0b4fb56a7 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 126c757e4cd46f866ddc283143b58eb4d9bf52cd (diff) | |
RDMA: Use ib_no_udata_io() in query_device callbacks
The query_device callbacks that neither accept driver-specific input nor
return a driver-specific response open-code the empty udata handling as
ib_is_udata_in_empty() on entry and ib_respond_empty_udata() on exit.
ib_no_udata_io() already combines both steps, so replace the entry check
with it and simply return 0 on success.
Unlike the create and destroy flows, query_device owns no uobject or HW
resource - the extended path fills a stack ib_device_attr that the core
discards on error - so clearing the empty response buffer on entry rather
than on exit is a mechanical change with no functional difference.
Link: https://patch.msgid.link/20260714-convert-to-noio-udata-v1-1-f1f6b6c7c988@nvidia.com
Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
