RFR: 8351661: NMT: VMATree should support separate call-stacks for reserve and commit operations [v25]

[Gerard Ziemski]

On Wed, 14 May 2025 08:19:34 GMT, Afshin Zafari <azafari at openjdk.org> wrote:

> > We have a single state denoting free region currently in vmatree, i.e.`State::Released` - should we make a distinction between: never touched and free vs released and free ?
> 
> In current NMT reports, only reserved regions and committed regions inside them are printed out. If we want to distinguish `never touched` and ` released` regions, we have to track `release` operations as well. We don't keep released regions in the tree right now. I vote 'no' to adding this feature to NMT.

No problem, this issue is related to the mtNone issue in my mind, i.e.:

mtNone vs mtUnknown (or mtUnused)

I think it would be nice to make distinction between, none never touched, and none don't care (we used it in the past, but now we don't care), but I'm not going to push for it.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/24028#issuecomment-2880613289