JasonAtNvidia

@shwina Building the package specifically for Jetson did work. ```bash git clone -b dev https://github.com/NVIDIA/NVTX.git cd NVTX/python C_INCLUDE_PATH=/usr/local/cuda-11.4/targets/aarch64-linux/include/ python3 setup.py bdist_conda ``` Should we have to do this considering the...

So the original reason for the --disable_nvtx flag was a build for Jetson in 2020 when Jetson Xavier release was CUDA 10.2 but NVTX did not exist on Jetson yet....

@shwina The nvtx from conda-forge didn't work on Jetson until I just built it specifically for Jetson just a few hours ago. It was failing originally, that is why I...

@vyasr I think we can close this issue as it is no longer relevant. You are correct that nvtx libraries are universally available libraries now.

The probability of a Jetson with a discrete GPU is ultra low and we can say that they don't exist outside of NVIDIA DRIVE units. We could easily wrap the...

Theoretically there is no device affinity on a Jetson, GPU and CPU share the same chunk of RAM and don't have to communicate via PCI bus.

There are Jetson boards with multiple GPU capability, DRIVE units are most common. They have a Xavier SoM and a Turing daughter board. The linux-4-tegra distribution has a file in...

@pentschev Yes, Jetson devices respond to the CUDA_VISIBLE_DEVICES environment variable. I do not have a Jetson device to test multiple GPUs with, but I am able to verify that CUDA_VISIBLE_DEVICES=0...

@pentschev I think your patch is good. It builds and loads on the Jetson device, and I think these are the 3 functions you touched with the patch. ``` >>>...