Re: [apache/tvm-rfcs] [UMA RFC] Discussion beyond UMA_v1.0 (PR #86)

Closed #86. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/86#event-7128966556 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/tvm-rfcs] [UMA RFC] Discussion beyond UMA_v1.0 (PR #86)

Reopened #86. -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/86#event-7128967862 You are receiving this because you are subscribed to this thread. Message ID:

[apache/tvm-rfcs] [UMA RFC] Discussion beyond UMA_v1.0 (PR #86)

You can view, comment on, or merge this pull request online at: https://github.com/apache/tvm-rfcs/pull/86 -- Commit Summary -- * [UMA RFC] added discussion beyoond UMA_v1.0 -- File Changes -- M rfcs/0060_UMA_Unified_Modular_Accelerator_Interface.md (97) A rfcs/assets/0060/uma_str

Re: [apache/tvm-rfcs] [RFC] UMA Universal Modular Accelerator Interface (PR #60)

Thanks @cgerum and @PaulPalomeroBernardo . I agree, this totally makes sense like this. @manupa-arm @areusch is this sufficiently detailed for you? I propose to discuss outstanding topics in meeting to settle for UMA-v1. We could use the Community Meeting on May 25th. Or if these discussions ar

Re: [apache/tvm-rfcs] [RFC] UMA Universal Modular Accelerator Interface (PR #60)

@areusch and @manupa-arm : For A2, we agree. [Target-registered compilation flow customization](https://github.com/apache/tvm-rfcs/blob/main/rfcs/0010-target-registered-compiler-flow-customisation.md) is the way to go here. CC: @cgerum @PaulPalomeroBernardo -- Reply to this email directly

[apache/tvm] [RFC][Tracking Issue] UMA: Universal Modular Accelerator Interface (Issue #11260)

This is a global tracking issue for landing the initial PRs of **UMA**. The original RFC can be found [here](https://github.com/boschresearch/tvm-rfcs/blob/rfc_uma/rfcs/00xx_UMA_Unified_Modular_Accelerator_Interface.md). Please feel free to bring in more questions to the corresponding thread. T

Re: [apache/tvm-rfcs] [RFC] UMA Universal Modular Accelerator Interface (PR #60)

> @MichaelJKlaiber is this one ready for another look? Sure 👍 -- Reply to this email directly or view it on GitHub: https://github.com/apache/tvm-rfcs/pull/60#issuecomment-1099088473 You are receiving this because you are subscribed to this thread. Message ID:

Re: [apache/tvm-rfcs] [RFC] UMA Universal Modular Accelerator Interface (PR #60)

> Thanks @MichaelJKlaiber, that makes sense. So I was wondering if this is the > case, perhaps in the future this interface is used by other backend's (not > accelerators) we would need to think about renaming UMA to something more > generic e.g. UMB _Universal Modular Backend_ - I'm not the bes

Re: [apache/tvm-rfcs] [RFC] UMA Universal Modular Accelerator Interface (PR #60)

> One overall question I have is whether this proposal is strictly limited to > accelerators or whether it could also be used by any back-end that leverages > the target hook functionality? For example, it seems possible to register > kernel libraries (e.g. CMSIS-NN) using a similar interface?

[Apache TVM Discuss] [Development/pre-RFC] [RFC] UMA: Universal Modular Accelerator Interface

PR in TVM-RFC: https://github.com/apache/tvm-rfcs/pull/60 --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-uma-universal-modular-accelerator-interface/12039/16) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here]

[apache/tvm-rfcs] Rfc uma (PR #60)

opening PR for UMA pre-RFC You can view, comment on, or merge this pull request online at: https://github.com/apache/tvm-rfcs/pull/60 -- Commit Summary -- * moving uma rfc from dicuss forum here * uma rfc update * Update 00xx_UMA_Unified_Modular_Accelerator_Interface.md * Merge pull re

[Apache TVM Discuss] [Development/pre-RFC] [RFC] UMA: Universal Modular Accelerator Interface

Thanks everyone for the detailed input and feedback! To keep track of the **latest version** of the UMA pre-RFC and to add the **great suggestions that we got from this discussion thread**, I created a document in our tvm-rfc fork : https://github.com/boschresearch/tvm-rfcs/blob/rfc_uma/rfcs/0

[Apache TVM Discuss] [Announcement] Unifying TVM and microTVM Community Meetings

Hi Andrew. :+1: Sounds good! --- [Visit Topic](https://discuss.tvm.apache.org/t/unifying-tvm-and-microtvm-community-meetings/12171/2) to respond. You are receiving this because you enabled mailing list mode. To unsubscribe from these emails, [click here](https://discuss.tvm.apache.org/

[Apache TVM Discuss] [Announcement] TVM Community Meeting, November 18 2021

Hi Chris, is there a plan when the next TVM Community Meeting is going to take place? Especially the "Remove CODEOWNERS" discussion seems to be a good fit for a high-bandwidth discussion: https://discuss.tvm.apache.org/t/rfc-remove-codeowners/12095/8 Thanks, Michael CC: @hogepodge @aca8

[Apache TVM Discuss] [Development/pre-RFC] [RFC] UMA: Universal Modular Accelerator Interface

@fPecc, Andrew @areusch has agreed to put it on the agenda of the next community meeting. Would be great to have as many interested community members there as possible to collect requirements and find a sweet spot for the API 👍. --- [Visit Topic](https://discuss.tvm.apache.org/t/rfc-uma-

[Apache TVM Discuss] [Development/pre-RFC] [RFC] UMA: Universal Modular Accelerator Interface

Andrew, thanks for the summary :) . Thanks everyone for the great discussion @cgerum @paulpb @philippvk @r.stahl @areusch @jroesch @mbs-octoml! [quote="areusch, post:6, topic:12039"] Partitioning: UMA is using the standard TVM partitioner, registering patterns using the pattern-table infras

[Apache TVM Discuss] [Development/pre-RFC] [RFC] UMA: Universal Modular Accelerator Interface

Thanks @areusch and @jroesch for the input and great questions on this PRE-RFC 👍. We really appreciate it. As this is a pre-RFC, we felt it is really important to get input from the TVM community as soon as possible :) . [quote="jroesch, post:2, topic:12039"] There has been talking of unifyin