[Diagnostics] Update dotnet-trace collect-linux and perfmap enablement (#54354)

* [Dotnet-Trace] Update glibc compatibility note

* [Diagnostics] Update PerfMap enable options

* update date

* Elaborate diagnostics IPC command options in table

* Address feedback

Author: mdh1418

docs/core/diagnostics/dotnet-trace.md

@@ -1,7 +1,7 @@
 ---
 title: dotnet-trace diagnostic tool - .NET CLI
 description: Learn how to install and use the dotnet-trace CLI tool to collect .NET traces of a running process without the native profiler, by using the .NET EventPipe.
-ms.date: 03/19/2026
+ms.date: 06/10/2026
 ms.topic: reference
 ms.custom: sfi-ropc-nochange
 ---
@@ -311,8 +311,8 @@ Collects diagnostic traces using perf_events, a Linux OS technology. `collect-li
 - .NET 10+
 
 > [!NOTE]
-> The `collect-linux` verb only runs on Linux x64 and Linux Arm64 environments that have glibc version 2.35 or later.
-> All of the [.NET 10 officially supported Linux distros](https://github.com/dotnet/core/blob/main/release-notes/10.0/supported-os.md#linux) support this requirement except Alpine 3.22, CentOS Stream 9, and any distros based off Red Hat Enterprise Linux 9.
+> The `collect-linux` verb only runs on Linux x64 and Linux Arm64 environments that have glibc version 2.27 or later.
+> All of the [.NET 10 officially supported Linux distros](https://github.com/dotnet/core/blob/main/release-notes/10.0/supported-os.md#linux) support this requirement except Alpine 3.22.
 > A quick way to check the version of a system's libc is with the command `ldd --version` or by executing the libc library directly.
 
 > [!TIP]

docs/core/runtime-config/debugging-profiling.md

@@ -1,7 +1,7 @@
 ---
 title: Debugging profiling config settings
 description: Learn about runtime settings that configure debugging and profiling for .NET apps.
-ms.date: 11/27/2019
+ms.date: 06/10/2026
 ---
 # Runtime configuration options for debugging and profiling
 
@@ -65,6 +65,7 @@ When the `DOTNET_PROFILER_PATH*` [environment variables](#environment-variable-c
 
 - Enables or disables perf maps or jit dumps. These files allow third party tools, such as the Linux `perf` tool, to provide human readable names for dynamically generated code and precompiled ReadyToRun (R2R) modules.
 - If you omit this setting, writing perf map and jit dump files are both disabled. This is equivalent to setting the value to `0`.
+- On .NET 8 and later, profiling tools can enable perfmaps on demand without needing any environment variable configuration. However not every profiling tool implements this. Manually setting the environment is still required for at least the Linux 'perf' tool and 'perfcollect'.
 - When perf maps are disabled, not all managed callsites will be properly resolved.
 - Depending on the Linux kernel version, both formats are supported by the `perf` tool.
 - Enabling perf maps or jit dumps might cause up to a 20% overhead, though often it's much less. To minimize performance impact, it's recommended to selectively enable either perf maps or jit dumps, but not both. The impact only occurs while the application is JITing code. Often that occurs at startup, but it might occur later if the application is running a new code path for the first time.