summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/bin
diff options
context:
space:
mode:
authorCaleb Sander Mateos <csander@purestorage.com>2025-12-12 10:17:05 -0700
committerJens Axboe <axboe@kernel.dk>2025-12-12 12:50:41 -0700
commit52bc483763262b66e51818a82e03cad0c5bfef67 (patch)
treee181b503bcffc7a920f0e90f4e40efe18f544309 /tools/perf/scripts/python/bin
parentd8295408e0cf529be78ee4ed8b6758a9fb209feb (diff)
selftests: ublk: forbid multiple data copy modes
The kublk mock ublk server allows multiple data copy mode arguments to be passed on the command line (--zero_copy, --get_data, and --auto_zc). The ublk device will be created with all the requested feature flags, however kublk will only use one of the modes to interact with request data (arbitrarily preferring auto_zc over zero_copy over get_data). To clarify the intent of the test, don't allow multiple data copy modes to be specified. --zero_copy and --auto_zc are allowed together for --auto_zc_fallback, which uses both copy modes. Don't set UBLK_F_USER_COPY for zero_copy, as it's a separate feature. Fix the test cases in test_stress_05 passing --get_data along with --zero_copy or --auto_zc. Signed-off-by: Caleb Sander Mateos <csander@purestorage.com> Reviewed-by: Ming Lei <ming.lei@redhat.com> Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions