jverma-quic commented on code in PR #12971: URL: https://github.com/apache/tvm/pull/12971#discussion_r995129105
########## src/runtime/hexagon/profiler/README.md: ########## @@ -0,0 +1,152 @@ +<!--- Licensed to the Apache Software Foundation (ASF) under one --> +<!--- or more contributor license agreements. See the NOTICE file --> +<!--- distributed with this work for additional information --> +<!--- regarding copyright ownership. The ASF licenses this file --> +<!--- to you under the Apache License, Version 2.0 (the --> +<!--- "License"); you may not use this file except in compliance --> +<!--- with the License. You may obtain a copy of the License at --> + +<!--- http://www.apache.org/licenses/LICENSE-2.0 --> + +<!--- Unless required by applicable law or agreed to in writing, --> +<!--- software distributed under the License is distributed on an --> +<!--- "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --> +<!--- KIND, either express or implied. See the License for the --> +<!--- specific language governing permissions and limitations --> +<!--- under the License. --> + +# Hexagon lightweight instrumentation based profiling (LWP) + +For Hexagon, LWP can be used to get function and loop level processor cycle count. +This is done by instrumenting the code with profiling builtin calls using a TIR pass. +During codegen, these builtin calls are replaced with the calls to a hexagon specific +handler which records the runtime information into a buffer. +This buffer is written into a JSON file ('lwp.json') which is processed to construct Review Comment: There is no easy way of getting the data from Hexagon. It needs to be saved into a file. Since this file contains the processor cycles for each handler invocation, it needs to be processed for ease of understanding. -- 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. To unsubscribe, e-mail: commits-unsubscr...@tvm.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
