Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Alan Bateman
On Thu, 31 Oct 2024 03:52:31 GMT, Dean Long wrote: > For some reason github thinks VirtualThreadPinnedEvent.java was renamed to > libSynchronizedNative.c and libTracePinnedThreads.c was renamed to > LockingMode.java. Is there a way to fix that? I don't think which view this is but just to say

Re: RFR: 8343132: Remove temporary transitions from Virtual thread implementation

2024-10-30 Thread David Holmes
On Mon, 28 Oct 2024 08:34:14 GMT, Alan Bateman wrote: > This is an update to the Virtual thread implementation that we'd like to > integrate in advance of JEP 491. > > The update removes the use of "temporary transitions", basically cases where > the thread identity switches to the carrier th

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Dean Long
On Wed, 30 Oct 2024 22:44:48 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v12]

2024-10-30 Thread Dean Long
On Tue, 29 Oct 2024 19:01:03 GMT, Patricio Chilano Mateo wrote: >>> One way to get rid of this would be to have c2 just set last_Java_pc too >>> along with last_Java_sp, so we don't need to push lr to be able to do >>> last_Java_sp[-1] to make the frame walkable. >> >> If that would solve the

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v17]

2024-10-30 Thread Dean Long
On Tue, 29 Oct 2024 22:15:16 GMT, Patricio Chilano Mateo wrote: >> src/hotspot/share/code/nmethod.cpp line 1302: >> >>> 1300: _compiler_type = type; >>> 1301: _orig_pc_offset = 0; >>> 1302: _num_stack_arg_slots = 0; >> >> Was the old value wrong, unneeded, or

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread David Holmes
On Thu, 31 Oct 2024 01:32:19 GMT, Dean Long wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Fix typos in comments > > src/hotspot/share/runtime/objectMonitor.inline.hpp line 207: > >> 205: } >> 206: >>

Re: RFR: 8341788: Fix ExceptionOccurred in hotspot [v2]

2024-10-30 Thread David Holmes
On Wed, 30 Oct 2024 20:31:44 GMT, Justin Lu wrote: >> Justin Lu has updated the pull request incrementally with one additional >> commit since the last revision: >> >> address other cases in Hotspot > > Thank you for the review. @justin-curtis-lu for future reference note that hotspot gener

Re: RFR: 8331497: Implement JEP 483: Ahead-of-Time Class Loading & Linking [v5]

2024-10-30 Thread Ioi Lam
> This is an implementation of [JEP 483: Ahead-of-Time Class Loading & > Linking](https://openjdk.org/jeps/483). > > > Note: this is a combined PR of the following individual PRs > - https://github.com/openjdk/jdk/pull/20516 > - https://github.com/openjdk/jdk/pull/20517 > - https://github.co

Re: RFR: 8331497: Implement JEP 483: Ahead-of-Time Class Loading & Linking [v6]

2024-10-30 Thread Ioi Lam
> This is an implementation of [JEP 483: Ahead-of-Time Class Loading & > Linking](https://openjdk.org/jeps/483). > > > Note: this is a combined PR of the following individual PRs > - https://github.com/openjdk/jdk/pull/20516 > - https://github.com/openjdk/jdk/pull/20517 > - https://github.co

Re: RFR: 8331497: Implement JEP 483: Ahead-of-Time Class Loading & Linking [v4]

2024-10-30 Thread Ioi Lam
On Fri, 25 Oct 2024 18:14:38 GMT, Ashutosh Mehra wrote: >> src/hotspot/share/classfile/systemDictionaryShared.cpp line 685: >> >>> 683: InstanceKlass* ik = InstanceKlass::cast(k); >>> 684: >>> 685: if (SafepointSynchronize::is_at_safepoint()) { >> >> Why is this piece of block required

Re: RFR: 8331497: Implement JEP 483: Ahead-of-Time Class Loading & Linking [v4]

2024-10-30 Thread Ioi Lam
On Fri, 25 Oct 2024 15:02:30 GMT, Ashutosh Mehra wrote: >> Ioi Lam has updated the pull request incrementally with two additional >> commits since the last revision: >> >> - 8342907: Implement AOT testing mode for jtreg tests (authored by >> @katyapav) >> - disable test that fails with hotsp

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Dean Long
On Wed, 30 Oct 2024 22:44:48 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Dean Long
On Wed, 30 Oct 2024 22:44:48 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Dean Long
On Wed, 30 Oct 2024 22:44:48 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v16]

2024-10-30 Thread Patricio Chilano Mateo
On Tue, 29 Oct 2024 23:05:20 GMT, Dean Long wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Fix comment in VThreadWaitReenter > > src/hotspot/share/runtime/continuationFreezeThaw.cpp line 696: > >> 694:

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v19]

2024-10-30 Thread Patricio Chilano Mateo
On Wed, 30 Oct 2024 19:06:58 GMT, Coleen Phillimore wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Add klass_name check for is_object_wait0 >> - Fix comment in continuation.hpp > > src/hotspot/share/r

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Dean Long
On Wed, 30 Oct 2024 22:11:38 GMT, Patricio Chilano Mateo wrote: >> src/hotspot/share/runtime/continuation.hpp line 50: >> >>> 48: class JavaThread; >>> 49: >>> 50: // should match Continuation.PreemptStatus() in Continuation.java >> >> As far as I can tell, these enum values still don't match

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Dean Long
On Wed, 30 Oct 2024 22:44:48 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v16]

2024-10-30 Thread Patricio Chilano Mateo
On Wed, 30 Oct 2024 19:02:05 GMT, Coleen Phillimore wrote: >> src/hotspot/share/runtime/continuationFreezeThaw.cpp line 1411: >> >>> 1409: // zero out fields (but not the stack) >>> 1410: const size_t hs = oopDesc::header_size(); >>> 1411: oopDesc::set_klass_gap(mem, 0); >> >> Why,

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v22]

2024-10-30 Thread Patricio Chilano Mateo
> This is the implementation of JEP 491: Synchronize Virtual Threads without > Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for > further details. > > In order to make the code review easier the changes have been split into the > following initial 4 commits: > > - Change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v16]

2024-10-30 Thread Patricio Chilano Mateo
On Tue, 29 Oct 2024 20:57:48 GMT, Dean Long wrote: >> No, it just happens to be stored at the sender_sp marker. We were already >> making room for two words but only using one. > > `sender_sp_offset` is listed under "All frames", but I guess that's wrong and > should be changed. Can we fix the

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v19]

2024-10-30 Thread Patricio Chilano Mateo
On Wed, 30 Oct 2024 00:52:32 GMT, Dean Long wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Add klass_name check for is_object_wait0 >> - Fix comment in continuation.hpp > > src/hotspot/cpu/x86/interp_

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v21]

2024-10-30 Thread Patricio Chilano Mateo
> This is the implementation of JEP 491: Synchronize Virtual Threads without > Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for > further details. > > In order to make the code review easier the changes have been split into the > following initial 4 commits: > > - Change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v21]

2024-10-30 Thread Patricio Chilano Mateo
On Wed, 30 Oct 2024 01:52:30 GMT, Dean Long wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - SmallRegisterMap::instance() fix + comment typo >> - Add comment in call_VM_preemptable > > src/hotspot/share

Integrated: 8337276: jcmd man page update for PID in output filenames

2024-10-30 Thread Kevin Walls
On Wed, 31 Jul 2024 08:30:47 GMT, Kevin Walls wrote: > Man page update for jcmd. > > Add updates for the filename options/arguments affected by: > 8334492: DiagnosticCommands (jcmd) should accept %p in output filenames and > substitute PID > > Also: > In the initial "command" summary, remove t

Integrated: 8341788: Fix ExceptionOccurred in hotspot

2024-10-30 Thread Justin Lu
On Fri, 25 Oct 2024 21:51:53 GMT, Justin Lu wrote: > A trivial JNI refactoring in Hotspot to use `ExceptionCheck()` over > `ExceptionOccurred()` when the usage is treating the return value as a > boolean. This is part of the bigger umbrella issue: > [JDK-8341542](https://bugs.openjdk.org/brows

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v20]

2024-10-30 Thread David Holmes
On Wed, 30 Oct 2024 20:16:52 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v9]

2024-10-30 Thread David Holmes
On Mon, 28 Oct 2024 22:02:02 GMT, Patricio Chilano Mateo wrote: >> That said such a scenario is not about concurrently pushing the same thread >> to the list from different threads. So I'm still somewhat confused about the >> concurrency control here. Specifically I can't see how the cmpxchg o

Re: RFR: 8341788: Fix ExceptionOccurred in hotspot [v2]

2024-10-30 Thread Justin Lu
On Tue, 29 Oct 2024 00:19:29 GMT, Justin Lu wrote: >> A trivial JNI refactoring in Hotspot to use `ExceptionCheck()` over >> `ExceptionOccurred()` when the usage is treating the return value as a >> boolean. This is part of the bigger umbrella issue: >> [JDK-8341542](https://bugs.openjdk.org/b

Re: RFR: 8331497: Implement JEP 483: Ahead-of-Time Class Loading & Linking [v4]

2024-10-30 Thread Ioi Lam
On Wed, 30 Oct 2024 19:11:46 GMT, Ioi Lam wrote: >> A thought for a possible cleanup, after this PR is done… >> >> The scratch mirror logic had me… scratching my head. It seems to me that a >> more descriptive name would make the code explain itself better. I suggest >> (for a future cleanup

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v16]

2024-10-30 Thread Patricio Chilano Mateo
On Tue, 29 Oct 2024 02:56:30 GMT, Serguei Spitsyn wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Fix comment in VThreadWaitReenter > > src/hotspot/share/prims/jvmtiEnvBase.cpp line 1082: > >> 1080:

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v3]

2024-10-30 Thread Sean Mullan
On Fri, 25 Oct 2024 20:44:25 GMT, Roger Riggs wrote: >> Sean Mullan has updated the pull request with a new target base due to a >> merge or a rebase. The pull request now contains 150 commits: >> >> - Merge remote-tracking branch 'jdk-sandbox/jep486' into JDK-8338411 >> - Merge >> - Update

Re: RFR: 8337276: jcmd man page update for PID in output filenames [v3]

2024-10-30 Thread Kevin Walls
On Thu, 17 Oct 2024 16:12:26 GMT, Kevin Walls wrote: >> Man page update for jcmd. >> >> Add updates for the filename options/arguments affected by: >> 8334492: DiagnosticCommands (jcmd) should accept %p in output filenames and >> substitute PID >> >> Also: >> In the initial "command" summary,

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v20]

2024-10-30 Thread Patricio Chilano Mateo
On Mon, 21 Oct 2024 09:55:53 GMT, Axel Boldt-Christmas wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Rename oopCont + fix in JvmtiUnmountBeginMark > > src/hotspot/share/runtime/continuationFreezeThaw.c

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v4]

2024-10-30 Thread Sean Mullan
On Tue, 29 Oct 2024 14:19:05 GMT, Weijun Wang wrote: >> test/jdk/javax/xml/crypto/dsig/ErrorHandlerPermissions.java line 1: >> >>> 1: /* >> >> @wangweij It looks like this test can be deleted as it was specifically >> trying to check that a `SecurityException` wasn't thrown, or did you think

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v20]

2024-10-30 Thread Patricio Chilano Mateo
> This is the implementation of JEP 491: Synchronize Virtual Threads without > Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for > further details. > > In order to make the code review easier the changes have been split into the > following initial 4 commits: > > - Change

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v19]

2024-10-30 Thread Patricio Chilano Mateo
On Wed, 30 Oct 2024 09:44:42 GMT, Serguei Spitsyn wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with two >> additional commits since the last revision: >> >> - Add klass_name check for is_object_wait0 >> - Fix comment in continuation.hpp > > src/hotspot/share/run

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v5]

2024-10-30 Thread Sean Mullan
On Tue, 29 Oct 2024 18:35:05 GMT, Brent Christian wrote: >> Sean Mullan has updated the pull request with a new target base due to a >> merge or a rebase. The pull request now contains 186 commits: >> >> - Merge remote-tracking branch 'jdk-sandbox/jep486' into JDK-8338411 >> - Update copyrigh

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v4]

2024-10-30 Thread Sean Mullan
On Mon, 28 Oct 2024 20:12:27 GMT, Roger Riggs wrote: > Reviewed all tests under test/jaxp/javax/xml/jaxp. A few imports moved around > unnecessarily but otherwise looks fine. JAXP test comments fixed in https://github.com/openjdk/jdk/pull/21498/commits/5577e4884710eba498ee5f40fa85d47eaa07364d

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v3]

2024-10-30 Thread Sean Mullan
On Fri, 25 Oct 2024 21:18:41 GMT, Sean Mullan wrote: > Comments on `java.security` classes. > > Also, I'd like to see some clarifications on what "the installed policy" or > "the current policy" is. The `ProtectionDomain` mentions this when talking > about dynamic permissions. On the other han

Re: RFR: 8337511: Implement JEP 404: Generational Shenandoah (Experimental) [v5]

2024-10-30 Thread William Kemper
On Wed, 30 Oct 2024 02:09:46 GMT, Liang Mao wrote: >> We disabled tiered compilation to force everything to compile through C2 to >> get more consistent results. > > @earthling-amzn ,thanks for providing your options. Looks like disabling > pacing would help the score. > > -XX:+UseShenandoahG

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Vladimir Kozlov
On Wed, 30 Oct 2024 11:18:27 GMT, Magnus Ihse Bursie wrote: >> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 >> Port_](https://openjdk.org/jeps/479). >> >> This is the summary of JEP 479: >>> Remove the source code and build support for the Windows 32-bit x86 port. >>>

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v3]

2024-10-30 Thread Sean Mullan
On Tue, 29 Oct 2024 17:07:56 GMT, Harshitha Onkar wrote: >> src/java.desktop/share/classes/java/awt/Font.java line 1613: >> >>> 1611: * interpreted as a {@code Font} object according to the >>> 1612: * specification of {@code Font.decode(String)} >>> 1613: * If the specified prope

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v6]

2024-10-30 Thread Sean Mullan
On Wed, 30 Oct 2024 19:28:32 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Vladimir Kozlov
On Wed, 30 Oct 2024 11:18:27 GMT, Magnus Ihse Bursie wrote: >> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 >> Port_](https://openjdk.org/jeps/479). >> >> This is the summary of JEP 479: >>> Remove the source code and build support for the Windows 32-bit x86 port. >>>

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Vladimir Kozlov
On Wed, 30 Oct 2024 11:18:27 GMT, Magnus Ihse Bursie wrote: >> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 >> Port_](https://openjdk.org/jeps/479). >> >> This is the summary of JEP 479: >>> Remove the source code and build support for the Windows 32-bit x86 port. >>>

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v16]

2024-10-30 Thread Coleen Phillimore
On Tue, 29 Oct 2024 23:16:29 GMT, Dean Long wrote: >> Patricio Chilano Mateo has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Fix comment in VThreadWaitReenter > > src/hotspot/share/runtime/continuationFreezeThaw.cpp line 1411: > >> 1409

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v19]

2024-10-30 Thread Coleen Phillimore
On Wed, 30 Oct 2024 00:44:14 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Vladimir Kozlov
On Wed, 30 Oct 2024 11:18:27 GMT, Magnus Ihse Bursie wrote: >> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 >> Port_](https://openjdk.org/jeps/479). >> >> This is the summary of JEP 479: >>> Remove the source code and build support for the Windows 32-bit x86 port. >>>

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v6]

2024-10-30 Thread Sean Mullan
> This is the implementation of JEP 486: Permanently Disable the Security > Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The > [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the > main changes in the JEP and also includes an apidiff of the specif

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Vladimir Kozlov
On Wed, 30 Oct 2024 11:18:27 GMT, Magnus Ihse Bursie wrote: >> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 >> Port_](https://openjdk.org/jeps/479). >> >> This is the summary of JEP 479: >>> Remove the source code and build support for the Windows 32-bit x86 port. >>>

Re: RFR: 8331497: Implement JEP 483: Ahead-of-Time Class Loading & Linking [v4]

2024-10-30 Thread Ioi Lam
On Thu, 24 Oct 2024 06:14:18 GMT, John R Rose wrote: > A thought for a possible cleanup, after this PR is done… > > The scratch mirror logic had me… scratching my head. It seems to me that a > more descriptive name would make the code explain itself better. I suggest > (for a future cleanup) c

Re: RFR: 8337276: jcmd man page update for PID in output filenames [v3]

2024-10-30 Thread Sonia Zaldana Calles
On Thu, 17 Oct 2024 16:12:26 GMT, Kevin Walls wrote: >> Man page update for jcmd. >> >> Add updates for the filename options/arguments affected by: >> 8334492: DiagnosticCommands (jcmd) should accept %p in output filenames and >> substitute PID >> >> Also: >> In the initial "command" summary,

Integrated: 8341927: Replace hardcoded security providers with new test.provider.name system property

2024-10-30 Thread Matthew Donovan
On Wed, 16 Oct 2024 18:47:44 GMT, Matthew Donovan wrote: > In this PR, I removed hard-coded security providers and replaced them with a > system property, test.provider.name. If the property is not specified, the > provider originally used in the test is used: > > Cipher c = Cipher.getInstance

Re: RFR: 8341927: Replace hardcoded security providers with new test.provider.name system property [v7]

2024-10-30 Thread Sean Mullan
On Wed, 30 Oct 2024 18:12:30 GMT, Matthew Donovan wrote: >> In this PR, I removed hard-coded security providers and replaced them with a >> system property, test.provider.name. If the property is not specified, the >> provider originally used in the test is used: >> >> Cipher c = Cipher.getIns

Integrated: 8343103: Enable debug logging for vmTestbase/nsk/jvmti/scenarios/sampling/SP05/sp05t003/TestDescription.java

2024-10-30 Thread Alex Menkov
On Fri, 25 Oct 2024 22:44:49 GMT, Alex Menkov wrote: > The fix enables logging in the test agent to get more details about > intermittent failures. This pull request has now been integrated. Changeset: 1b177ce5 Author:Alex Menkov URL: https://git.openjdk.org/jdk/commit/1b177ce5b7e2

Re: RFR: 8341927: Replace hardcoded security providers with new test.provider.name system property [v7]

2024-10-30 Thread Matthew Donovan
> In this PR, I removed hard-coded security providers and replaced them with a > system property, test.provider.name. If the property is not specified, the > provider originally used in the test is used: > > Cipher c = Cipher.getInstance("AES/GCM/NoPadding", > System.getProperty("test.provider.

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v13]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 12:11:26 GMT, Aleksey Shipilev wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Fix 32/64-bit confusion in comment in VirtualMachineImpl.c > > make/hotspot/gensrc/GensrcAdlc.gmk line 50: >

Re: RFR: 8342449: reimplement: JDK-8327114 Attach in Linux may have wrong behavior when pid == ns_pid [v3]

2024-10-30 Thread Kevin Walls
On Wed, 30 Oct 2024 17:20:49 GMT, Larry Cable wrote: >> the implementation I originally provided does not in fact solve the issue! >> >> the attach protocol initiation "handshake" requires that the "attacher" (the >> caller of this code) and the "attachee"(the target JVM to be "attached" to) >

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v19]

2024-10-30 Thread Coleen Phillimore
On Wed, 30 Oct 2024 00:44:14 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8341927: Replace hardcoded security providers with new test.provider.name system property [v6]

2024-10-30 Thread Sean Mullan
On Wed, 30 Oct 2024 14:48:46 GMT, Matthew Donovan wrote: >> In this PR, I removed hard-coded security providers and replaced them with a >> system property, test.provider.name. If the property is not specified, the >> provider originally used in the test is used: >> >> Cipher c = Cipher.getIns

Re: RFR: 8341927: Replace hardcoded security providers with new test.provider.name system property [v6]

2024-10-30 Thread Rajan Halade
On Wed, 30 Oct 2024 14:48:46 GMT, Matthew Donovan wrote: >> In this PR, I removed hard-coded security providers and replaced them with a >> system property, test.provider.name. If the property is not specified, the >> provider originally used in the test is used: >> >> Cipher c = Cipher.getIns

Re: RFR: 8342449: reimplement: JDK-8327114 Attach in Linux may have wrong behavior when pid == ns_pid [v3]

2024-10-30 Thread Larry Cable
> the implementation I originally provided does not in fact solve the issue! > > the attach protocol initiation "handshake" requires that the "attacher" (the > caller of this code) and the "attachee"(the target JVM to be "attached" to) > *must* share a "/tmp" (or access to the attachee's `cwd`)

Re: RFR: 8341927: Replace hardcoded security providers with new test.provider.name system property [v6]

2024-10-30 Thread Matthew Donovan
> In this PR, I removed hard-coded security providers and replaced them with a > system property, test.provider.name. If the property is not specified, the > provider originally used in the test is used: > > Cipher c = Cipher.getInstance("AES/GCM/NoPadding", > System.getProperty("test.provider.

Re: RFR: 8304824: NMT should not use ThreadCritical [v9]

2024-10-30 Thread Robert Toyonaga
On Mon, 28 Oct 2024 16:12:39 GMT, Robert Toyonaga wrote: >> ### 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

Integrated: 8202100: Merge vm/share/InMemoryJavaCompiler w/ jdk/test/lib/compiler/InMemoryJavaCompiler

2024-10-30 Thread Ramkumar Sunderbabu
On Tue, 22 Oct 2024 15:52:27 GMT, Ramkumar Sunderbabu wrote: > Merging vm folder's InMemoryJavaCompiler into jdk folder's merge > InMemoryJavaCompiler so that maintenance is easy. > > Testing done for > Tiers 1,2,3 > test/hotspot/jtreg tests This pull request has now been integrated. Changes

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 12:30:25 GMT, Julian Waters wrote: >> I'm glad you're giving some TLC to adlc. It is in desperate need of it. > > TLC? https://www.vocabulary.com/dictionary/TLC - PR Review Comment: https://git.openjdk.org/jdk/pull/21744#discussion_r1822628499

Re: RFR: 8304824: NMT should not use ThreadCritical [v9]

2024-10-30 Thread Thomas Stuefe
On Mon, 28 Oct 2024 16:12:39 GMT, Robert Toyonaga wrote: >> ### 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

Re: RFR: 8304824: NMT should not use ThreadCritical [v9]

2024-10-30 Thread Thomas Stuefe
On Mon, 28 Oct 2024 16:12:39 GMT, Robert Toyonaga wrote: >> ### 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

Re: RFR: 8337276: jcmd man page update for PID in output filenames [v3]

2024-10-30 Thread Chris Plummer
On Thu, 17 Oct 2024 16:12:26 GMT, Kevin Walls wrote: >> Man page update for jcmd. >> >> Add updates for the filename options/arguments affected by: >> 8334492: DiagnosticCommands (jcmd) should accept %p in output filenames and >> substitute PID >> >> Also: >> In the initial "command" summary,

Re: RFR: 8304824: NMT should not use ThreadCritical [v9]

2024-10-30 Thread Robert Toyonaga
On Mon, 28 Oct 2024 16:12:39 GMT, Robert Toyonaga wrote: >> ### 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

Re: RFR: 8304824: NMT should not use ThreadCritical [v3]

2024-10-30 Thread Johan Sjölen
On Wed, 30 Oct 2024 13:39:00 GMT, Robert Toyonaga wrote: >I'm not certain, but looking at it again, it seems that the ThreadCritical >uses in ChunkPool::deallocate_chunk and ChunkPool::prune() are only needed for >NMT and are independent of the other ThreadCritical uses in that code. At least

Re: RFR: 8342449: reimplement: JDK-8327114 Attach in Linux may have wrong behavior when pid == ns_pid [v2]

2024-10-30 Thread Kevin Walls
On Tue, 29 Oct 2024 19:08:12 GMT, Larry Cable wrote: >> src/jdk.attach/linux/classes/sun/tools/attach/VirtualMachineImpl.java line >> 114: >> >>> 112: String.format("Unable to open socket file %s: >>> " + >>> 113: "target process %d doesn't res

Re: RFR: 8341927: Replace hardcoded security providers with new test.provider.name system property [v5]

2024-10-30 Thread Sean Mullan
On Wed, 30 Oct 2024 13:09:26 GMT, Matthew Donovan wrote: >> In this PR, I removed hard-coded security providers and replaced them with a >> system property, test.provider.name. If the property is not specified, the >> provider originally used in the test is used: >> >> Cipher c = Cipher.getIns

Re: RFR: 8343132: Remove temporary transitions from Virtual thread implementation

2024-10-30 Thread Patricio Chilano Mateo
On Mon, 28 Oct 2024 08:34:14 GMT, Alan Bateman wrote: > This is an update to the Virtual thread implementation that we'd like to > integrate in advance of JEP 491. > > The update removes the use of "temporary transitions", basically cases where > the thread identity switches to the carrier th

Re: RFR: 8304824: NMT should not use ThreadCritical [v3]

2024-10-30 Thread Robert Toyonaga
On Wed, 30 Oct 2024 12:32:17 GMT, Johan Sjölen wrote: >>> Hi @tstuefe, >>> >>> > Ah thank you. I think I added that printing ages ago. I should not have >>> > used tty. The immediate solution to get you going may be to just change >>> > this from tty to fileStream fs(stderr); >>> >>> Thanks!

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v13]

2024-10-30 Thread Aleksey Shipilev
On Tue, 29 Oct 2024 20:22:03 GMT, Magnus Ihse Bursie wrote: >> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 >> Port_](https://openjdk.org/jeps/479). >> >> This is the summary of JEP 479: >>> Remove the source code and build support for the Windows 32-bit x86 port. >>>

Re: RFR: 8341927: Replace hardcoded security providers with new test.provider.name system property [v5]

2024-10-30 Thread Matthew Donovan
> In this PR, I removed hard-coded security providers and replaced them with a > system property, test.provider.name. If the property is not specified, the > provider originally used in the test is used: > > Cipher c = Cipher.getInstance("AES/GCM/NoPadding", > System.getProperty("test.provider.

Re: RFR: 8304824: NMT should not use ThreadCritical [v3]

2024-10-30 Thread Johan Sjölen
On Wed, 18 Sep 2024 05:53:05 GMT, Thomas Stuefe wrote: >> Hi @roberttoyonaga >> >> (Pinging @afshin-zafari and @jdksjolen) >> >> First off, it is good that you ran into this since it highlights a possible >> real deadlock. Both locks are quite coarse. I cannot think from the top of >> my hea

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Julian Waters
On Wed, 30 Oct 2024 11:19:03 GMT, Magnus Ihse Bursie wrote: >> src/hotspot/share/adlc/main.cpp line 494: >> >>> 492: } >>> 493: >>> 494: #if !defined(_WIN32) || defined(_WIN64) >> >> Removing the conditionalization is fine for this change. But see also >> https://bugs.openjdk.org/browse/JDK-

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v13]

2024-10-30 Thread Aleksey Shipilev
On Wed, 30 Oct 2024 11:05:17 GMT, Magnus Ihse Bursie wrote: >> make/scripts/compare.sh line 1457: >> >>> 1455: THIS_SEC_BIN="$THIS_SEC_DIR/sec-bin.zip" >>> 1456: if [ "$OPENJDK_TARGET_OS" = "windows" ]; then >>> 1457: JGSS_WINDOWS_BIN="jgss-windows-x64-bin.zip" >> >>

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 03:24:48 GMT, Kim Barrett wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Error in os_windows.cpp for unknown cpu > > src/java.base/windows/native/libjava/gdefs_md.h line 31: > >> 29: >>

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Magnus Ihse Bursie
> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 > Port_](https://openjdk.org/jeps/479). > > This is the summary of JEP 479: >> Remove the source code and build support for the Windows 32-bit x86 port. >> This port was [deprecated for removal in JDK >> 21](https://openjd

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 03:13:02 GMT, Kim Barrett wrote: >> It's something we do in our build. For us, _LP64 really means 64 bit > > It seems like the `_WIN64` check here was never useful. It's also been there > since before the > mercurial age. The "mercurial age". Sounds like something in-betwee

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v15]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 03:05:32 GMT, Kim Barrett wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Error in os_windows.cpp for unknown cpu > > src/hotspot/share/adlc/main.cpp line 494: > >> 492: } >> 493: >> 494

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v12]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 00:07:33 GMT, Kim Barrett wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one >> additional commit since the last revision: >> >> adlc need _CRT_NONSTDC_NO_WARNINGS as well... *sigh* > > src/hotspot/cpu/x86/sharedRuntime_x86_32.cpp line 1433: >

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v14]

2024-10-30 Thread Magnus Ihse Bursie
> This is the implementation of [JEP 479: _Remove the Windows 32-bit x86 > Port_](https://openjdk.org/jeps/479). > > This is the summary of JEP 479: >> Remove the source code and build support for the Windows 32-bit x86 port. >> This port was [deprecated for removal in JDK >> 21](https://openjd

Re: RFR: 8341692: Implement JEP 490: ZGC: Remove the Non-Generational Mode [v5]

2024-10-30 Thread Axel Boldt-Christmas
On Fri, 25 Oct 2024 08:25:21 GMT, Axel Boldt-Christmas wrote: >> This is the implementation task for `JEP 490: ZGC: Remove the >> Non-Generational Mode`. See the JEP for details. >> [JDK-8335850](https://bugs.openjdk.org/browse/JDK-8335850) > > Axel Boldt-Christmas has updated the pull request

Integrated: 8341692: Implement JEP 490: ZGC: Remove the Non-Generational Mode

2024-10-30 Thread Axel Boldt-Christmas
On Tue, 8 Oct 2024 07:20:49 GMT, Axel Boldt-Christmas wrote: > This is the implementation task for `JEP 490: ZGC: Remove the > Non-Generational Mode`. See the JEP for details. > [JDK-8335850](https://bugs.openjdk.org/browse/JDK-8335850) This pull request has now been integrated. Changeset: 8

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v13]

2024-10-30 Thread Magnus Ihse Bursie
On Tue, 29 Oct 2024 23:48:22 GMT, Kim Barrett wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Fix 32/64-bit confusion in comment in VirtualMachineImpl.c > > make/scripts/compare.sh line 79: > >> 77: >> 78:

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v13]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 02:18:00 GMT, David Holmes wrote: >> Yes. As Julian says, it's something we set up in our builds: >> >> if test "x$FLAGS_CPU_BITS" = x64; then >> $1_DEFINES_CPU_JDK="${$1_DEFINES_CPU_JDK} -D_LP64=1" >> $1_DEFINES_CPU_JVM="${$1_DEFINES_CPU_JVM} -D_LP64=1" >> fi > >

Re: RFR: 8339783: Implement JEP 479: Remove the Windows 32-bit x86 Port [v13]

2024-10-30 Thread Magnus Ihse Bursie
On Wed, 30 Oct 2024 02:23:20 GMT, David Holmes wrote: >> Magnus Ihse Bursie has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Fix 32/64-bit confusion in comment in VirtualMachineImpl.c > > src/hotspot/os_cpu/windows_x86/os_windows_x86.cpp

Re: RFR: 8341692: Implement JEP 490: ZGC: Remove the Non-Generational Mode [v5]

2024-10-30 Thread Magnus Ihse Bursie
On Fri, 25 Oct 2024 08:25:21 GMT, Axel Boldt-Christmas wrote: >> This is the implementation task for `JEP 490: ZGC: Remove the >> Non-Generational Mode`. See the JEP for details. >> [JDK-8335850](https://bugs.openjdk.org/browse/JDK-8335850) > > Axel Boldt-Christmas has updated the pull request

Re: RFR: 8338383: Implement JEP 491: Synchronize Virtual Threads without Pinning [v19]

2024-10-30 Thread Serguei Spitsyn
On Wed, 30 Oct 2024 00:44:14 GMT, Patricio Chilano Mateo wrote: >> This is the implementation of JEP 491: Synchronize Virtual Threads without >> Pinning. See [JEP 491](https://bugs.openjdk.org/browse/JDK-8337395) for >> further details. >> >> In order to make the code review easier the change

Re: RFR: 8338411: Implement JEP 486: Permanently Disable the Security Manager [v5]

2024-10-30 Thread Athijegannathan Sundararajan
On Tue, 29 Oct 2024 12:40:59 GMT, Sean Mullan wrote: >> This is the implementation of JEP 486: Permanently Disable the Security >> Manager. See [JEP 486](https://openjdk.org/jeps/486) for more details. The >> [CSR](https://bugs.openjdk.org/browse/JDK-8338412) describes in detail the >> main ch