[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-serviceability-dev
Subject:    Integrated: 8264166: OopStorage should support specifying MEMFLAGS for allocations
From:       Kim Barrett <kbarrett () openjdk ! java ! net>
Date:       2021-03-26 7:47:46
Message-ID: 0lZbxFyo0UuHHM2ew5Nz_YhCj75hw_3VGG2oGeMEZdU=.d60f7968-1cba-4a6b-97a4-1043f8ab1bb9 () github ! com
[Download RAW message or body]

On Thu, 25 Mar 2021 07:27:58 GMT, Kim Barrett <kbarrett@openjdk.org> wrote:

> Please review this change to OopStorage to allow the MEMFLAGS value for associated \
> allocations to be specified when the storage object is constructed.  This allows a \
> subsystem that needs an OopStorage object to associate its allocation with others \
> for that subsystem in NMT tracking and reporting. 
> Testing:
> mach5 tier1.
> Manually compared NMT output before and after this change for a test that generated \
> a lot of one particular OopStorage entries.

This pull request has now been integrated.

Changeset: bb354b9d
Author:    Kim Barrett <kbarrett@openjdk.org>
URL:       https://git.openjdk.java.net/jdk/commit/bb354b9d
Stats:     64 lines in 16 files changed: 30 ins; 0 del; 34 mod

8264166: OopStorage should support specifying MEMFLAGS for allocations

Reviewed-by: tschatzl, stefank

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

PR: https://git.openjdk.java.net/jdk/pull/3188


[prev in list] [next in list] [prev in thread] [next in thread]