[QST] How to output iket trace

[deciding]

I am using iket.range_push/pop, and I expect to get a trace json at the end of kernel execution. but I haven't. may i know what is the expected usage/behaviour of using iket in device event recording?

[brandon-yujie-sun]

Thanks for the question @deciding We will share more documentations on IKET in the upcoming release, stay tuned :-)

[magicwyzh]

Hi @deciding, there is a run-iket tool released together with cuteDSL 4.6 as the main profiler tool to collect iket data. By default all iket ops in the kernel codes take no effect unless the run-iket profiler attached, they will be translated to fine tuned profiling codes.

An example cmd to run profiler is like below:

OUTPUT_DIR="${OUTPUT_DIR:-./iket_output}"

# Run IKET profiling
run-iket \
    --output-dir "$OUTPUT_DIR" \
    profile \
    --postprocess all \
    -- <app-command>

with 'postprocess all' it will generate both json output and perfetto traces.

More detailed doc will be released soon