RFR: 8356228: NMT does not record reserved memory base address correctly

Afshin Zafari azafari at openjdk.org
Thu Jun 12 10:12:28 UTC 2025


On Wed, 11 Jun 2025 08:55:30 GMT, Stefan Karlsson <stefank at openjdk.org> wrote:

> > NMT ignores tracking of releasing CDS regions that are contained in larger regions, because they should be in a specific order.
> 
> The special-case handling of CDS in NMT breaks abstractions and has caused a number of bugs. I'm worried that trying to workaround this special-case code makes the code even more susceptible for future bugs. So, therefore I'm interested to here about the planes you have to replace the NMT implementation with a tree. Isn't that going to remove the CDS special-case code and maybe be even solve this issue without the need for this fix? If not, feel free to ignore my comment.

In the new implementation of NMT with tree, there will be no special-case handling neither for CDS nor for any other memory types. Thanks for bringing this up.

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

PR Comment: https://git.openjdk.org/jdk/pull/25719#issuecomment-2965999494


More information about the hotspot-runtime-dev mailing list