Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Fixed
Priority: P4
Fix Version/s: 25
Affects Version/s: None
Component/s: hotspot
Labels:
- nmt

Subcomponent:
runtime
Resolved In Build:
master

This is a followup to ~~JDK-8328944~~, which addressed some cases where mtNone showed up in reports, but there is more to do here.

Here we mainly concentrate on removing the default parameter, so that no-one is tempted to use the APIs without providing the mem tag, if known.

causes

JDK-8354545 [arm32] Build broken since JDK-8344883

Closed

is cloned by

JDK-8354535 [BACKOUT] Force clients to explicitly pass mem_tag value, even if it is mtNone

Resolved

JDK-8354547 REDO: Force clients to explicitly pass mem_tag value, even if it is mtNone

Open

relates to

JDK-8353477 Skip default value parameter if it's false from os::reserve_memory_special and os::attempt_reserve_memory_at()

Open

JDK-8328944 NMT reports "unknown" memory

Resolved

JDK-8353480 Replace mtNone with actual values, when known

Open

links to

Commit(master) openjdk/jdk/43b19474

Review(master) openjdk/jdk/24282

(1 relates to, 2 links to)

Assignee:: Gerard Ziemski

Reporter:: Gerard Ziemski

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2024-11-22 10:55

Updated:: 2 days ago 12:32

Resolved:: 2 days ago 09:24

Details

Description

Attachments

Issue Links

Activity

People

Dates