Skip to content

feat(ccu): add direct runtime engine - #75

Draft
Kur0x wants to merge 2 commits into
codex/ccu-stack-03-installfrom
codex/ccu-stack-04-runtime
Draft

feat(ccu): add direct runtime engine#75
Kur0x wants to merge 2 commits into
codex/ccu-stack-03-installfrom
codex/ccu-stack-04-runtime

Conversation

@Kur0x

@Kur0x Kur0x commented Jul 28, 2026

Copy link
Copy Markdown
Member

Summary

  • add the direct CCU runtime lifecycle and public-runtime launch boundary
  • add the direct orchestrator on top of the install-provider stack
  • retain TileXR-owned types and avoid hcomm or HCCL private APIs

Stack

4 of 9. Depends on codex/ccu-stack-03-install.

Validation

  • git diff --check
  • focused direct-orchestrator and RA-loader unit tests
  • 36 tests passed; 13 CANN or later-layer cases skipped

Scope

This PR adds the engine only. Communicator and collectives integration follows in the next PR.

class TileXRCcuDirectRuntime {
public:
int Init(const TileXRCcuDirectRuntimeOptions& options, TileXRCcuDirectRuntimeReport* report);
void Shutdown();

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please make this owning runtime RAII by adding a destructor that calls Shutdown() (and keep it non-copyable). Once initialized it owns registered memory/token handles plus channel/CQ/QP/import handles; allowing the object to leave scope without an explicit shutdown leaks those resources, and TileXRCcuHccpLoader cleanup does not release them.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants