-
Notifications
You must be signed in to change notification settings - Fork 453
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
Qualcomm AI Engine Direct - Support QNN 2.28 #6811
Qualcomm AI Engine Direct - Support QNN 2.28 #6811
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/6811
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 259cbc9 with merge base 7010a11 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
6ae5b16
to
dd1836e
Compare
What feature is used from 2.28? |
Based on Qnn 2.28 release note, they seem to improve the latency for large models. |
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
f2f9c84
to
e7eba31
Compare
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Do we know if static llama and llama transformer will still work with this version bump? Also we need to figure out a plan to do version bump without bc breaking... |
Our tests for static llama all are on this version. About bc breaking, I think that we could add some macros around the code which only support on 2.28 to make sure that users could build libqnnexecutorch on older qnn version. Is it acceptable? |
Yeah that sounds good. BC is something we can figure out later. Just hope it can be part of the plan. |
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Hi sorry for being a bit back and forth here - Context is that the pre-generated .pte file will no longer be compatible. If the work isn't too much, how likely we can make this PR bc compatible? If there is too much work, we can try to merge this. |
Thank you for your response. I apologize for any confusion. What I meant is that if we merge this PR, libqnnexecutorch will not be able to build with QNN versions earlier than 2.28. However, the pre-generated .pte files should still be supported. The build issue arises in cases like this: QNN_SYSTEM_CONTEXT_BINARY_INFO_VERSION_3 only exists in headers from version 2.28 onwards. If you try to build with version 2.26, you'll encounter an error stating that QNN_SYSTEM_CONTEXT_BINARY_INFO_VERSION_3 cannot be found. |
If possible, please go ahead and merge this PR. We will discuss internally whether to add some macros around the code that only supports version 2.28 and later, to ensure that users can build libqnnexecutorch on older QNN versions. |
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
e7eba31
to
6096504
Compare
Note that if merged, QNN version less than 2.28 will not support it.
6096504
to
259cbc9
Compare
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Hi @cccclai, |
@cccclai has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
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! Inform the internal team and merging now
Differential Revision: D65949627 Pull Request resolved: #6811
Note that if merged, QNN version less than 2.28 will not support it.