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

[Afshin Zafari]

On Tue, 18 Mar 2025 10:04:15 GMT, Johan Sjölen <jsjolen at openjdk.org> wrote:

> We need a better definition of what is supposed to happen in these cases

It depends what we want to print in the report. Currently it is like this:

[A-B] reserved from 
  [mem address] function_1
  [mem address] function_2
     [X-Y] committed from 
        [mem address] function_3
        [mem address] function_4 

which shows the stack for 'reserved region' only once. Then, for every sub-region inside that it shows the committed regions with their stacks. IOW, not all the commits have 'reserved'-stack.

We can define a new report that would be like this:

Region [A-X], Reserved , mtXXX, stack_1
Region [X-Y], Reserved and Committed, stack_2
Region [Y-B], Reserved , mtXXX, stack_1

or something similar. 

Which form of output do we want to have in the report?

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

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