-
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
[Target] Fix device mask issue and typos #9768
Conversation
09e1f9d
to
8683a6a
Compare
@@ -217,13 +216,15 @@ class Device(ctypes.Structure): | |||
"stackvm": 1, | |||
"cpu": 1, | |||
"c": 1, | |||
"hybrid": 1, |
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.
what is hybrid?
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.
Not sure about it. There is no comment or RFC.
https://github.com/apache/tvm/blob/main/src/target/target_kind.cc#L400-L401
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.
@masahi there is a legacy thing called TE hybrid script. Probably it’s related?
* [Target] Fix device mask issue and typos * Skip target hook
* [Target] Fix device mask issue and typos * Skip target hook
Hi Community,
Currently, I am working on the Heterogeneous Execution by using
Composite Target
. I found it is not included in theDevice.STR2MASK
map and will be failed when compiling with it. So, I added it back and checked all the other targets. Not surprisingly, there are some other issues. Now, I add aConsistency verification case
to help us check it. :)In addition to these, I still have some doubts.
Target System
, the device type is saved in each Target (tvm.target.Target.kind
). It seems that some attributes of the Device inruntime_ctypes.py
are redundant, such asMASK2STR
andSTR2MASK
. Then the issue raised here is the same or equaled features located in different locations make things messy. I think we can refactor theRuntime Device
.Composite Target
cannot be optimized or even recognized by all relay passes. Ideally, thePartition Pass
can perform the partitioning and annotation automatically based on those devices (order does matter), and then select the best op strategy. So my question is: What is the current status forComposite Target
and is anyone working on it?Any help would be much appreciated. :)