Skip to content

[origami] Add catastrophic fallback to rank_configs#8793

Open
bethune-bryant wants to merge 1 commit into
developfrom
users/bnelson/rank-configs-catastrophic-fallback
Open

[origami] Add catastrophic fallback to rank_configs#8793
bethune-bryant wants to merge 1 commit into
developfrom
users/bnelson/rank-configs-catastrophic-fallback

Conversation

@bethune-bryant

Copy link
Copy Markdown
Contributor

Summary

  • When rank_configs rejects every candidate (LDS/RF capacity or max latency), fall back to ranking the invalid configs instead of throwing No valid configs found.
  • Split candidates into valid_configs and invalid_configs, with a shared compute_ranked_latency helper for GEMM and attention paths.
  • Trim verbose tie-breaker debug logging and document the new behavior in origami.hpp.

Test plan

  • ./tests/origami-tests "Origami: rank_configs unit test" (36 assertions)
  • All-invalid LDS configs return max-latency fallback ranking
  • Mixed valid + LDS/heuristic-rejected configs rank only valid candidates (gfx950)
  • All-rejected LDS + heuristic path uses catastrophic fallback (gfx950)

Made with Cursor

When every candidate is rejected by capacity or latency checks, rank the
invalid configs instead of throwing so selection can still return a kernel.

Co-authored-by: Cursor <cursoragent@cursor.com>
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

❌ Your project status has failed because the head coverage (77.89%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #8793   +/-   ##
========================================
  Coverage    71.50%   71.50%           
========================================
  Files         2612     2612           
  Lines       407895   407895           
  Branches     60982    60982           
========================================
  Hits        291636   291636           
  Misses       94875    94875           
  Partials     21384    21384           
Flag Coverage Δ *Carryforward flag
TensileLite 76.92% <ø> (ø) Carriedforward from 3bda378
hipBLAS 90.81% <ø> (ø) Carriedforward from 3bda378
hipBLASLt 41.36% <ø> (ø)
hipCUB 82.68% <ø> (ø) Carriedforward from 3bda378
hipDNN 86.74% <ø> (ø) Carriedforward from 3bda378
hipFFT 50.17% <ø> (ø) Carriedforward from 3bda378
hipRAND 76.12% <ø> (ø) Carriedforward from 3bda378
hipSOLVER 69.18% <ø> (ø) Carriedforward from 3bda378
hipSPARSE 86.55% <ø> (ø) Carriedforward from 3bda378
rocBLAS 48.49% <ø> (ø) Carriedforward from 3bda378
rocFFT 47.16% <ø> (ø) Carriedforward from 3bda378
rocRAND 57.07% <ø> (ø) Carriedforward from 3bda378
rocSOLVER 77.89% <ø> (ø) Carriedforward from 3bda378
rocSPARSE 72.37% <ø> (ø) Carriedforward from 3bda378
rocThrust 91.35% <ø> (ø) Carriedforward from 3bda378

*This pull request uses carry forward flags. Click here to find out more.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants