make GC's PAL implementation include the right dump info

[Maoni0]

since we want to use GC's own PAL impl for all GC build flavors I took a look at it to see if there's any gaps. the only gap seems to be the dump info where we call madvise to include committed memory (MADV_DODUMP) and exclude reserved/reset memory (MADV_DONTDUMP). after we add those calls we should be good to go.

CC @janvorli @mangod9

Tagging subscribers to this area: @dotnet/gc
See info in area-owners.md if you want to be subscribed.

Issue Details

---

since we want to use GC's own PAL impl for all GC build flavors I took a look at it to see if there's any gaps. the only gap seems to be the dump info where we call madvise to include committed memory (MADV_DODUMP) and exclude reserved/reset memory (MADV_DONTDUMP). after we add those calls we should be good to go.

CC @janvorli @mangod9

Author:	Maoni0
Assignees:	-
Labels:	area-GC-coreclr
Milestone:	-

[mangod9]

I have added a call to madvise here: a585fc3. Dont believe MADV_DONTDUMP is required for the GC case. @janvorli ?

[mangod9]

Oh I guess its required for the reserve case. Will update.

[mangod9]

have updated the PR to include the MADV_DONTDUMP though VirtualDecommit seems to need more changes as mentioned here: #76985 (comment)

[Maoni0]

fixed by 76985