Refactor: gate Scheduler summary log behind PTO2_SCHED_PROFILING

[ChaoWao]

Summary

Follow-up to #1217. The per-thread Scheduler summary device log was
emitted under plain PTO2_PROFILING=1 (Level 1), while every other
per-thread profiling line (orch_* / sched_* timing) is gated by its
Level 2/3 sub-macro. That made Level 1 the only level producing a
per-thread device log, and left the profiling_levels.md per-level counts
inconsistent (CodeRabbit flagged this on #1217).

This moves Scheduler summary (and the sched_total computation that only
feeds it) into the #if PTO2_SCHED_PROFILING block in
log_l2_swimlane_summary() for both a2a3 and a5. Level 1 now emits no
per-thread device logs — it only feeds the host-side Orch/Sched
[STRACE] windows via aicpu_phase_set_window.

Changes

• Code (scheduler_cold_path.cpp, a2a3 + a5): gate Scheduler summary
  and sched_total behind PTO2_SCHED_PROFILING; mark cur_thread_completed
[[maybe_unused]] (now used only inside the SCHED block) to keep the
  Level-1 build clean under -Werror=unused-parameter.
• Docs (profiling_levels.md, a2a3 + a5): Level 1 documents zero device
  logs; Level 2 gains the Scheduler summary; the stale per-level
  LOG_INFO_V9 count formulas (N_sched*2 + N_orch*1 + 1,
  11 debug + 2 basic + ..., table count 7) are replaced with per-thread
  descriptions matching the actual macro gating.

Testing

• Default build clean on a2a3 and a5 (no -Werror=unused-variable/parameter)
• profiling-flags-smoke matrix reproduced locally: pto2-off / orch /
  orch-tensormap / sched / orch-sched / all-on all build on a2a3sim + a5sim
• dummy_task sim test passes on a2a3sim and a5sim
• Hardware tests (CI)

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[coderabbitai]

Warning

Review limit reached

@ChaoWao, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 461a558c-36b5-4f25-b399-b35de0c25161

📥 Commits

Reviewing files that changed from the base of the PR and between da79b70 and 5fe1b0c.

📒 Files selected for processing (4)

• src/a2a3/runtime/tensormap_and_ringbuffer/docs/profiling_levels.md
• src/a2a3/runtime/tensormap_and_ringbuffer/runtime/scheduler/scheduler_cold_path.cpp
• src/a5/runtime/tensormap_and_ringbuffer/docs/profiling_levels.md
• src/a5/runtime/tensormap_and_ringbuffer/runtime/scheduler/scheduler_cold_path.cpp

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}