-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[VTA][OpenCL] add device_annot support in graphpack #6125
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To prevent accidental PR merged given that this depends on #6124, I'm setting it to "changes requested"
e2eedb2
to
d25d0f3
Compare
@tmoreau89 Thanks for reviewing #6124. Shall we start review this PR? |
@zhanghaohit thanks for the ping, @ZihengJiang can you help me review this PR? |
# a fake on_device schedule. | ||
# this will not be used in actual computation | ||
# as on_device will be removed during DeviceAnnotation pass | ||
register_injective_schedule("on_device") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zhanghaohit what happens if we don't register this annotation op schedule?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It will raise
AssertionError: on_device doesn't have FTVMStrategy registered
during build_module.cc::Optimize before we do the RunDeviceAnnotationPass
.
I am wondering whether VTA's graph annotation can be unified into the relay's heterogeneous execution feature: #4178 |
2e7c08b
to
27dab34
Compare
ping @ZihengJiang |
Please fix the CI issue @zhanghaohit |
27dab34
to
20f0470
Compare
Fixed. Thanks @ZihengJiang @tmoreau89 for the review. |
ping @tmoreau89 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @zhanghaohit LGTM
* add device_annot support in graphpack * on_device annotation * lint * typo * fix lint * fix lint
* add device_annot support in graphpack * on_device annotation * lint * typo * fix lint * fix lint
* add device_annot support in graphpack * on_device annotation * lint * typo * fix lint * fix lint
This is related to #5840 and split from PR #5842
This PR depends on #6124 to work.
The new API allows to tag ext_dev device type from annot_start_name and annot_end_name