tt-metal: [$200 BOUNTY] creating 2 kernels on the same core in one program should error out
Create a program, add a kernel twice, eg:
auto dm0a = tt_metal::CreateKernel(
program,
"path",
cores,
tt_metal::DataMovementConfig{
.processor = tt_metal::DataMovementProcessor::RISCV_0
});
auto dm0b = tt_metal::CreateKernel(
program,
"path",
cores,
tt_metal::DataMovementConfig{
.processor = tt_metal::DataMovementProcessor::RISCV_0
});
The above should error out - creating 2 kernels running on the same cores should fail. Test should cover DM and COMPUTE and a variety of overlaps, eg, create both on a single core, create one on many cores and the other on just of those, or a set of those, etc.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (7 by maintainers)
Commits related to this issue
- Checking for duplicate core usage, by identifying RISCV type overlaps at core indicies, finding where overlaps lie. Addressing issue #6754 <https://github.com/tenstorrent/tt-metal/issues/6754> Iterat... — committed to lateralcoders/tt-metal by abin555 2 years ago
- Check for Duplicate Cores - Issue #6754 (#20907) ### Ticket [Link to Github Issue](https://github.com/tenstorrent/tt-metal/issues/6754) ### Problem description Copied from issue: Create a program,... — committed to jasondavies/tt-metal by abin555 a year ago
- Check for Duplicate Cores - Issue #6754 (#20907) ### Ticket [Link to Github Issue](https://github.com/tenstorrent/tt-metal/issues/6754) ### Problem description Copied from issue: Create a program,... — committed to jasondavies/tt-metal by abin555 a year ago
- Check for Duplicate Cores - Issue #6754 (#20907) ### Ticket [Link to Github Issue](https://github.com/tenstorrent/tt-metal/issues/6754) ### Problem description Copied from issue: Create a program,... — committed to tenstorrent/tt-metal by abin555 a year ago
This issue is complete, I’ll close when the merge goes through
email for bounty payment (remove the underscores please)
b_e_n@zutepredictive.comThanks!
Hello, great! Glad you are making progress. The new test(s) should go under the “api” subdir. Search the
tests/tt_metal/tt_metal/apisub dirs for “EXPECT_ANY_THROW” or “ASSERT_ANY_THROW”. See also: https://google.github.io/googletest/reference/assertions.htmlHey @benjaminmatthews!
I am happy to assign this bounty to you. And when it comes to payment, either of your can personally receive the payment and share the reward as you see fit.
Be sure that you read over the BOUNTY TERMS, as you agree to all of them by picking up this issue.
If we haven’t received any communication from you in a two week period, we will re-assign the issue, and you will no longer be eligible for completion of this bounty.
If you have any questions feel free to ping me here on this issue! Look forward to seeing your submission.