Pinned object heap impact on profilers

[davmason]

Overview issue in https://github.com/dotnet/runtime/issues/35561

After #32283 we have another GC heap for pinned objects. This will require at least the addition of a new entry to COR_PRF_GC_GENERATION and might require more work. This issue is tracking the investigation of any impact on profilers.

Tagging subscribers to this area: @tommcdon
Notify danmosemsft if you want to be subscribed.

[davmason]

The enum value was already added, still need to investigate any remaining impact though

[davmason]

After doing some investigation, there is no work needed for the profiler. It will have impact on profilers since they may not expect the new generation, but there is no runtime work necessary.

[noahfalk]

David, re-opening this issue to make sure we've also considered if testing needs to be added and if the enum has been documented?

[davmason]

I don't believe there is any testing that needs added at this point, and the documentation is done. Closing this issue