gpu: Add InstrumentedSamplingConfig to GpuCounterConfig

[dreveman]

Add counter_names field to GpuCounterConfig as an alternative to
counter_ids for selecting counters by name.

Add InstrumentedSamplingConfig with activity filtering support:

• ActivityNameFilter message with per-filter NameBase enum and
  name_glob field for matching mangled or demangled kernel names.
• TX range include/exclude globs for filtering by in-process
  annotations (e.g. NVTX ranges for CUDA).
• ActivityRange for skip/count based sampling of matching activities.
• Three-step filtering pipeline: activity name filters, TX range
  include/exclude, then range-based sampling.

Add instrumented sampling documentation to docs/data-sources/gpu.md.

[github-actions]

🎨 Perfetto UI Builds

• ba14781 (2026-03-31 16:49 UTC): https://storage.googleapis.com/perfetto-ci-artifacts/gh-23808907010-1-ui/ui/index.html
• ffd789f (2026-03-31 22:41 UTC): https://storage.googleapis.com/perfetto-ci-artifacts/gh-23822727780-1-ui/ui/index.html
• 631c90a (2026-04-01 20:55 UTC): https://storage.googleapis.com/perfetto-ci-artifacts/gh-23870051791-1-ui/ui/index.html
• 2ce4101 (2026-04-02 16:36 UTC): https://storage.googleapis.com/perfetto-ci-artifacts/gh-23910755723-1-ui/ui/index.html
• 9721306 (2026-04-15 13:37 UTC): https://storage.googleapis.com/perfetto-ci-artifacts/gh-24457559448-1-ui/ui/index.html

[LalitMaganti]

@olehkuznetsov - this might need more discussion or at least comments for Android indicating what is supported etc.

I think in general, this CL could also do with more description of which path you would want to choose, what options will be choose if you use the boolean option etc.

Also I think we need to start thinking about adding documentation to docs.perfetto.dev about all the things you are adding. We didn't add it before but you're significantly expanding the surface, I think it's worth us properly looking into this now.

[dreveman]

@olehkuznetsov - this might need more discussion or at least comments for Android indicating what is supported etc.

I think in general, this CL could also do with more description of which path you would want to choose, what options will be choose if you use the boolean option etc.

Also I think we need to start thinking about adding documentation to docs.perfetto.dev about all the things you are adding. We didn't add it before but you're significantly expanding the surface, I think it's worth us properly looking into this now.

Yes, I've been thinking about how to best do this. Just updating the docs/data_sources/gpu.md is a good start. I was thinking we have 3 sections in there:

• Common GPU things at the top
• Android specific things
• High performance GPGPU (e.g. latest Nvidia hw used for GenAI training and inference)

I'll start this as a separate change if that sounds good?

I was also thinking that the last bullet point could be added to the built-in examples so it's easy to see how perfetto UI can visualize these workloads.

[dreveman]

@LalitMaganti @olehkuznetsov Does the latest version of this look good to you?

[LalitMaganti]

Looks good to me. Giving owners approval but please wait for olehkuznetsov@ to confirm.

[dreveman]

@olehkuznetsov, friendly ping for review

[dreveman]

@olehkuznetsov, any chance you can take a look at this today? I'd like to update the Rust SDK proto bindings now that everything else has landed and it would be nice to include this.

@LalitMaganti, if olehkuznetsov is not available, how do you feel about me landing this now and following up if needed when olehkuznetsov has had a chance to review the final version of this?

[LalitMaganti]

I'd prefer to wait here if possible.