Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect error message when setting configure flag: --enable-nvtx-trace-per-dev #477

Open
ryanhankins opened this issue Jul 26, 2024 · 2 comments

Comments

@ryanhankins
Copy link
Contributor

When I run configure as follows:

./configure --prefix=/home/users/hankinsr/perf/aws-ofi-nccl/build --with-libfabric=/opt/cray/libfabric/1.15.2.0/ --with-hwloc=/home/users/hankinsr/perf/hwloc/build --with-cuda=/opt/nvidia/hpc_sdk/Linux_x86_64/23.11/cuda/12.3 --enable-nvtx-trace-per-dev --with-nvtx=/opt/nvidia/hpc_sdk/Linux_x86_64/23.3/cuda/12.0/targets/x86_64-linux

I get the following error message:

configure: error: Error: setting both nvtx_trace_per_comm and nvtx_trace_per_dev is currently not supported

But I'm only specifying -per-dev!

@rauteric
Copy link
Contributor

Hi! Yes, we should improve this. nvtx_trace_per_comm currently always defaults to 1 (

[nvtx_trace_per_comm=1
nvtx_trace_per_dev=0
), but we should make it default to 1 only when neither of the trace_per_comm nor trace_per_dev options is specified.

In the mean time, you can add --disable-nvtx-trace-per-comm.

@aws-nslick
Copy link
Contributor

@rauteric is a build option the correct way to do this? nsight has flags which can filter events to specific domains/etc., it might be overall simpler to remove these build-time tunables and make it all-or-nothing on our end, but tag them on different domains and then provide instructions on how to only enable one or the other.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants