On Mon, 17 Mar 2025 16:20:42 GMT, Robert Toyonaga wrote:
> ### Summary:
> This PR makes memory operations atomic with NMT accounting.
>
> ### The problem:
> In memory related functions like `os::commit_memory` and `os::reserve_memory`
> the OS memory operations are currently done before acquiri
On Mon, 24 Mar 2025 15:08:01 GMT, Kevin Walls wrote:
>> These tests have always silently permitted a -1 return value from
>> OperatingSystemMXBean CPU time methods.
>>
>> They need to be stricter, but occasionally Windows 2019 returns a -1 for the
>> first few calls of these methods. This see
On Mon, 24 Mar 2025 10:13:34 GMT, Kevin Walls wrote:
> These tests have always silently permitted a -1 return value from
> OperatingSystemMXBean CPU time methods.
>
> They need to be stricter, but occasionally Windows 2019 returns a -1 for the
> first few calls of these methods. This seems to
On Mon, 17 Mar 2025 16:20:42 GMT, Robert Toyonaga wrote:
> ### Summary:
> This PR makes memory operations atomic with NMT accounting.
>
> ### The problem:
> In memory related functions like `os::commit_memory` and `os::reserve_memory`
> the OS memory operations are currently done before acquiri
### Summary:
This PR makes memory operations atomic with NMT accounting.
### The problem:
In memory related functions like `os::commit_memory` and `os::reserve_memory`
the OS memory operations are currently done before acquiring the the NMT mutex.
And the the virtual memory accounting is done la
On Mon, 24 Mar 2025 16:16:34 GMT, Stefan Karlsson wrote:
>> ### Summary:
>> This PR makes memory operations atomic with NMT accounting.
>>
>> ### The problem:
>> In memory related functions like `os::commit_memory` and
>> `os::reserve_memory` the OS memory operations are currently done before
> These tests have always silently permitted a -1 return value from
> OperatingSystemMXBean CPU time methods.
>
> They need to be stricter, but occasionally Windows 2019 returns a -1 for the
> first few calls of these methods. This seems to be a Windows 2019 bug or
> peculiarity. Other Window
AIX changes for attach API to support arbitrary length arguments and the
streaming output support.
serviceability/attach/AttachAPIv2/StreamingOutputTest.java test passes
tier1, tier2 and tier3 testing is successful with fastdebug level
JBS Issue : [JDK-8352392](https://bugs.openjdk.org/browse/J
These tests have always silently permitted a -1 return value from
OperatingSystemMXBean CPU time methods.
They need to be stricter, but occasionally Windows 2019 returns a -1 for the
first few calls of these methods. This seems to be a Windows 2019 bug or
peculiarity. Other Windows versions a
