Runtime support for CPU hoist ops #2152
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vwellsTT
changed the title
vwellsTT
added a commit
that referenced
this pull request
Feb 19, 2025
### Problem description This PR adds support for CPU hoisting changes to our TTNNToFlatbuffer translation. ### What's changed This PR introduces new flatbuffer fields for CPU hoisted ops. It hooks up the TTNNToFlatbuffer pass to properly utilize passes introduced in other PRs s.t. a CPU dylib can be embedded in our flatbuffer. Note: this PR is pretty much impossible to test standalone, unfortunately. 2 following PRs will be strictly dependent on this PR merging: 1. #2148 this PR adds earlier support for hoisting in the TTNNPipeline for TTIRToTTNN. However, this generates IR that TTNNToFlatbuffer pass cannot parse until this PR lands. (So this TTNNToFlatbuffer PR is useless without TTIRToTTNN PR, but TTIRToTTNN breaks ttmlir-translate without this PR 😄 ). 2. #2152 Runtime PR, which will add support for actually executing new flatbuffers. This is obviously dependent on this PR + its flatbuffer changes as well.
vwellsTT
added a commit
that referenced
this pull request
Feb 20, 2025
### Problem description This PR adds support for CPU hoisting changes to our TTNNToFlatbuffer translation. ### What's changed This PR introduces new flatbuffer fields for CPU hoisted ops. It hooks up the TTNNToFlatbuffer pass to properly utilize passes introduced in other PRs s.t. a CPU dylib can be embedded in our flatbuffer. Note: this PR is pretty much impossible to test standalone, unfortunately. 2 following PRs will be strictly dependent on this PR merging: 1. #2148 this PR adds earlier support for hoisting in the TTNNPipeline for TTIRToTTNN. However, this generates IR that TTNNToFlatbuffer pass cannot parse until this PR lands. (So this TTNNToFlatbuffer PR is useless without TTIRToTTNN PR, but TTIRToTTNN breaks ttmlir-translate without this PR 😄 ). 2. #2152 Runtime PR, which will add support for actually executing new flatbuffers. This is obviously dependent on this PR + its flatbuffer changes as well.
vwellsTT
force-pushed
the
vwells/cpu_hoist_runtime
branch
from
1ea72a8 to
2fbe384
Compare
vwellsTT
force-pushed
the
vwells/cpu_hoist_runtime
branch
from
2fbe384 to
d947859
Compare
vwellsTT
commented
Feb 21, 2025
vwellsTT
commented
Feb 21, 2025
vwellsTT
commented
Feb 21, 2025
vwellsTT
commented
Feb 21, 2025
vwellsTT
requested review from
ctodTT,
jnie-TT,
kmabeeTT,
AleksKnezevic,
pilkicTT,
sdjordjevicTT,
svuckovicTT,
mtopalovicTT,
jserbedzijaTT,
azecevicTT,
tapspatel and
vprajapati-tt
as code owners
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
ctodTT
requested changes
Mar 6, 2025
ctodTT
approved these changes
Mar 6, 2025
jnie-TT
reviewed
Mar 6, 2025
| @@ -171,6 +175,11 @@ class ProgramContext { | |||
|
|
|||
| DeviceVariant getTargetDevice(uint32_t meshId); | |||
|
|
|||
| void *tryGetDylibHandle(const uint32_t dylibId) { | |||
There was a problem hiding this comment.
Nit: I think we can drop the const here and use uint32_t directly
There was a problem hiding this comment.
we definitely can but I'm not sure it's preferable. Personally, I prefer primitives to be const wherever possible, including params. But I don't super strongly I guess, our code is very const-unfriendly in general thanks to MLIR
svuckovicTT
approved these changes
Mar 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem description
Add runtime support for executing hoisted CPU ops.
What's changed
Add mechanism for reading + opening dylibs from flatbuffer, executing CPU ops (by executing proper function within a given dylib).
Checklist
Verify emptyOp logic works correctlyseparate follow-on PR to support empty tensors on host: Create specific TTNN op for empty tensor on host #2006