RFR: 8304824: NMT should not use ThreadCritical [v7]
Robert Toyonaga
duke at openjdk.org
Thu Sep 26 12:29:14 UTC 2024
> ### Summary
> This PR just replaces `ThreadCritical` with a lock specific to NMT. `ThreadCritical` is a big lock and is unnecessary for the purposes of NMT. I've implemented the new lock with a semaphore so that it can be used early before VM init. There is also the possibility of adding assertions in places we expect NMT to have synchronization. I haven't added assertions yet in many places because some code paths such as the (NMT tests) don't lock yet. I think it makes sense to close any gaps in locking in another PR in which I can also add more assertions.
>
> Testing:
> - hotspot_nmt
> - gtest:VirtualSpace
> - tier1
Robert Toyonaga has updated the pull request incrementally with one additional commit since the last revision:
Rename lock and mutex locker. Add back ThreadCritical when protecting mtChunk.
-------------
Changes:
- all: https://git.openjdk.org/jdk/pull/20852/files
- new: https://git.openjdk.org/jdk/pull/20852/files/07a2f4c2..88e075d1
Webrevs:
- full: https://webrevs.openjdk.org/?repo=jdk&pr=20852&range=06
- incr: https://webrevs.openjdk.org/?repo=jdk&pr=20852&range=05-06
Stats: 55 lines in 14 files changed: 9 ins; 16 del; 30 mod
Patch: https://git.openjdk.org/jdk/pull/20852.diff
Fetch: git fetch https://git.openjdk.org/jdk.git pull/20852/head:pull/20852
PR: https://git.openjdk.org/jdk/pull/20852
More information about the serviceability-dev
mailing list