Re: RFR: 8365192: post_meth_exit should be in vm state when calling get_jvmti_thread_state [v3]

On Fri, 5 Sep 2025 16:08:13 GMT, Leonid Mesnik wrote: >> This is the second attempt to fix method `post_meth_exit` to correctly set >> state and preserve result. >> The related fix here: >> https://github.com/openjdk/jdk/commit/b7b64bb6c800b45e32ff37b1b92b5927a3b3fb56 >> Hope fix became clarere

RFR: 8367014: Rename class Atomic to AtomicAccess

Please review this change that renames the all-static class `Atomic` to `AtomicAccess`. The reason for this name change is to allow the introduction of the new type `Atomic` ([JDK-8367013](https://bugs.openjdk.org/browse/JDK-8367013)). The PR has several commits, according to the specific categor

Re: RFR: 8365190: Remove LockingMode related code from share [v3]

On Thu, 4 Sep 2025 12:10:01 GMT, Fredrik Bredberg wrote: >> Since the integration of >> [JDK-8359437](https://bugs.openjdk.org/browse/JDK-8359437) the `LockingMode` >> flag can no longer be set by the user. After that, a number of PRs has been >> integrated which has removed all `LockingMode`

Integrated: 8366694: Test JdbStopInNotificationThreadTest.java timed out after 60 second

On Tue, 2 Sep 2025 15:10:52 GMT, SendaoYan wrote: > Hi all, > > Test com/sun/jdi/JdbStopInNotificationThreadTest.java fails "Exception thrown > during test execution: waitForPrompt timed out after 60 seconds" after > JDK-8260555 change the default timeout factor from 4 to 1. Before > JDK-8260

Re: RFR: 8366694: Test JdbStopInNotificationThreadTest.java timed out after 60 second [v3]

On Wed, 3 Sep 2025 01:49:04 GMT, SendaoYan wrote: >> Hi all, >> >> Test com/sun/jdi/JdbStopInNotificationThreadTest.java fails "Exception >> thrown during test execution: waitForPrompt timed out after 60 seconds" >> after JDK-8260555 change the default timeout factor from 4 to 1. Before >> JD

Re: RFR: 8365190: Remove LockingMode related code from share [v3]

On Thu, 4 Sep 2025 12:10:01 GMT, Fredrik Bredberg wrote: >> Since the integration of >> [JDK-8359437](https://bugs.openjdk.org/browse/JDK-8359437) the `LockingMode` >> flag can no longer be set by the user. After that, a number of PRs has been >> integrated which has removed all `LockingMode`

Re: RFR: 8366695: Test sun/jvmstat/monitor/MonitoredVm/MonitorVmStartTerminate.java timed out

On Wed, 3 Sep 2025 18:46:23 GMT, Kevin Walls wrote: >> Hi all, >> >> Test sun/jvmstat/monitor/MonitoredVm/MonitorVmStartTerminate.java create 10 >> java processes, and maybe this cause this test timed out when run this test >> with other jtreg tests concurrently. Though the run time statistics

Re: RFR: 8365190: Remove LockingMode related code from share

On Tue, 2 Sep 2025 20:19:06 GMT, Coleen Phillimore wrote: >> Since the integration of >> [JDK-8359437](https://bugs.openjdk.org/browse/JDK-8359437) the `LockingMode` >> flag can no longer be set by the user. After that, a number of PRs has been >> integrated which has removed all `LockingMode`

Re: RFR: 8365190: Remove LockingMode related code from share [v3]

On Thu, 4 Sep 2025 11:19:14 GMT, Coleen Phillimore wrote: >> Even calling it "lightweight locking" is no longer needed. > > I think the name "lightweight locking" is used for the file name and class > name, so the name is okay. It does help if you're trying to understand the > history of the l

Re: RFR: 8366780: Enhance ProcSmapsParser and Printer to handle THPeligible field [v3]

On Fri, 5 Sep 2025 08:33:38 GMT, Stefan Johansson wrote: >> Please review this enhancement to the smaps parser and printer. >> >> **Summary** >> While working on [JDK-8366434](https://bugs.openjdk.org/browse/JDK-8366434) >> one idea for a test to verify if the heap CAN be backed by transparent