areusch commented on pull request #7742:
URL: https://github.com/apache/tvm/pull/7742#issuecomment-807144342


   hi @stoa, thanks for your contribution! I agree with @tqchen an RFC would be 
great.
   
   looking over the code I see a lot of concepts implemented that are fairly 
similar to what we have implemented in microTVM now:
    - a remote execution driver
    - a project generation script
    - a minimal C runtime, including graph runtime and c_backend_api.h 
implementation
   
   For microTVM, we're taking the approach of reusing C runtime components 
between platforms and/or SoCs, and allowing platform-specific e.g. memory 
allocators by implementing `include/tvm/runtime/crt/platform.h`. We are also 
adopting a standard "interface layer" between TVM and generated firmware code 
(composed of "Model Library Format," "Project API," and the "TVM RPC server"), 
which provides a great way to reduce boilerplate code when targeting µC.
   
   It would be great if we could consider a way to unify your approach with our 
microTVM approach. It seems like the STM32 firmware code could become an 
implementation of our Project API (similar to the 
[host](https://github.com/areusch/incubator-tvm/tree/project-generator/src/runtime/crt/host)
 demo project). This would allow us to bring further improvements to TVM 
currently under development (e.g. AOT runtime, graph-level optimization, `tvmc` 
integration), as well as enable AutoTVM on your platform.
   
    Here are some pointers to RFCs that describe our approach in more detail:
    - [microTVM M2 
roadmap](https://discuss.tvm.apache.org/t/tvm-microtvm-m2-roadmap/8821)
    - [Model Library Format 
RFC](https://discuss.tvm.apache.org/t/rfc-tvm-model-library-format/9121), now 
committed
    - [Project Generator API 
RFC](https://discuss.tvm.apache.org/t/rfc-tvm-project-api/9449), PoC 
[here](https://github.com/areusch/incubator-tvm/tree/project-generator).
    - [AOT Runtime 
RFC](https://discuss.tvm.apache.org/t/implementing-aot-in-tvm/9206)
   
   Please also feel free to suggest improvements or changes to our current 
implementation. It is very much in development and we would like to encourage 
contributions!


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to