mirror of
https://github.com/saymrwulf/pytorch.git
synced 2026-05-14 20:57:59 +00:00
c25e33789e
Summary: Resubmit #20698 which got messed up. Idea is that when PyTorch is used in a custom build environment (e.g. Facebook), it's useful to track usage of various APIs centrally. This PR introduces a simple very lightweight mechanism to do so - only first invocation of a trigger point would be logged. This is significantly more lightweight than #18235 and thus we can allow to put logging in e.g. TensorImpl. Also adds an initial list of trigger points. Trigger points are added in such a way that no static initialization triggers them, i.e. just linking with libtorch.so will not cause any logging. Further suggestions of what to log are welcomed. Pull Request resolved: https://github.com/pytorch/pytorch/pull/20745 Differential Revision: D15429196 Pulled By: dzhulgakov fbshipit-source-id: a5e41a709a65b7ebccc6b95f93854e583cf20aca |
||
|---|---|---|
| .. | ||
| hip | ||
| math | ||
| threadpool | ||
| bench_utils.cc | ||
| bench_utils.h | ||
| cast.h | ||
| cast_test.cc | ||
| cblas.h | ||
| CMakeLists.txt | ||
| conversions.h | ||
| cpu_neon.h | ||
| cpuid.cc | ||
| cpuid.h | ||
| cpuid_test.cc | ||
| eigen_utils.h | ||
| fatal_signal_asan_no_sig_test.cc | ||
| filler.h | ||
| fixed_divisor.h | ||
| fixed_divisor_test.cc | ||
| GpuBitonicSort.cuh | ||
| GpuDefs.cuh | ||
| GpuScanUtils.cuh | ||
| map_utils.h | ||
| math-detail.h | ||
| math.h | ||
| math_cpu.cc | ||
| math_gpu.cu | ||
| math_gpu_test.cc | ||
| math_test.cc | ||
| murmur_hash3.cc | ||
| murmur_hash3.h | ||
| proto_convert.cc | ||
| proto_convert.h | ||
| proto_utils.cc | ||
| proto_utils.h | ||
| proto_utils_test.cc | ||
| proto_wrap.cc | ||
| proto_wrap.h | ||
| signal_handler.cc | ||
| signal_handler.h | ||
| simple_queue.h | ||
| simple_queue_test.cc | ||
| smart_tensor_printer.cc | ||
| smart_tensor_printer.h | ||
| smart_tensor_printer_test.cc | ||
| string_utils.cc | ||
| string_utils.h | ||
| zmq_helper.h | ||