Re: RFR: 8242427: JVMTI frame pop operations should use Thread-Local Handshakes

2020-09-02 Thread Yasumasa Suenaga
Hi Serguei, On 2020/09/02 15:29, David Holmes wrote: Hi Serguei, On 2/09/2020 4:11 pm, serguei.spit...@oracle.com wrote: Hi Yasumasa, It seems to me your update for sync with the JvmtiThreadState_lock is incorrect. Let me explain it. The original design was that the functions is_frame_pop, se

Re: RFR: 8242427: JVMTI frame pop operations should use Thread-Local Handshakes

2020-09-02 Thread serguei.spit...@oracle.com
Hi David, On 9/1/20 23:29, David Holmes wrote: Hi Serguei, On 2/09/2020 4:11 pm, serguei.spit...@oracle.com wrote: Hi Yasumasa, It seems to me your update for sync with the JvmtiThreadState_lock is incorrect. Let me explain it. The original design was that the functions is_frame_pop, set_

Re: RFR: 8242427: JVMTI frame pop operations should use Thread-Local Handshakes

2020-09-02 Thread David Holmes
Hi Serguei, On 2/09/2020 5:10 pm, serguei.spit...@oracle.com wrote: Hi David, On 9/1/20 23:29, David Holmes wrote: Hi Serguei, On 2/09/2020 4:11 pm, serguei.spit...@oracle.com wrote: Hi Yasumasa, It seems to me your update for sync with the JvmtiThreadState_lock is incorrect. Let me expl

Re: RFR: 8242427: JVMTI frame pop operations should use Thread-Local Handshakes

2020-09-02 Thread serguei.spit...@oracle.com
Hi David, On 9/2/20 00:32, David Holmes wrote: Hi Serguei, On 2/09/2020 5:10 pm, serguei.spit...@oracle.com wrote: Hi David, On 9/1/20 23:29, David Holmes wrote: Hi Serguei, On 2/09/2020 4:11 pm, serguei.spit...@oracle.com wrote: Hi Yasumasa, It seems to me your update for sync with the

Re: RFR: 8242427: JVMTI frame pop operations should use Thread-Local Handshakes

2020-09-02 Thread serguei.spit...@oracle.com
Hi Yasumasa, Thank you for the explanation. At least, I see the real motivation. I've overlooked this in the email thread. Thanks, Serguei On 9/2/20 00:00, Yasumasa Suenaga wrote: Hi Serguei, On 2020/09/02 15:29, David Holmes wrote: Hi Serguei, On 2/09/2020 4:11 pm, serguei.spit...@oracle.

Re: RFR: 8242427: JVMTI frame pop operations should use Thread-Local Handshakes

2020-09-02 Thread David Holmes
Hi Serguei, I have to confess I am not at all clear eactly what interactions the JvmtiThreadState_lock is supposed to serializing. :( I'm no longer convinced that holding that lock in place of executing at a safepoint is either necessary nor sufficient. David On 2/09/2020 6:38 pm, serguei.

Re: RFR(S): 8252407: Build failure with gcc-8+ and asan

2020-09-02 Thread Andrew Haley
On 01/09/2020 09:57, David Holmes wrote: > We already build with gcc 9.2 and don't see any issues with shared code > compiling for hotspot - which of these require --enable-asan? It > certainly looks like an unnecessary warning - the whole point of strncpy > is to truncate at a safe length. :( Yes

Re: RFR: 8242427: JVMTI frame pop operations should use Thread-Local Handshakes

2020-09-02 Thread serguei.spit...@oracle.com
Hi David, I do not see any obvious problems yet. But let me double-check everything tomorrow. Thanks, Serguei On 9/2/20 02:14, David Holmes wrote: Hi Serguei, I have to confess I am not at all clear eactly what interactions the JvmtiThreadState_lock is supposed to serializing. :( I'm no l

RE: RFR(L) 8227745: Enable Escape Analysis for Better Performance in the Presence of JVMTI Agents

2020-09-02 Thread Reingruber, Richard
Hi Robbin, // taking the discussion back to the mailing lists > I still don't understand why you don't deoptimize the objects inside the > handshake/safepoint instead? This is unfortunately not possible. Deoptimizing objects includes reallocating scalar replaced objects, i.e. calling Deopti

Re: RFR(S): 8252407: Build failure with gcc-8+ and asan

2020-09-02 Thread Eric Liu
Hi David, Thanks for your review and sorry for the delay. David Holmes on Tue Sep 1 08:57:01 UTC 2020 > We already build with gcc 9.2 and don't see any issues with shared code > compiling for hotspot - which of these require --enable-asan? It > certainly looks like an unnecessary warning - th

RFR(XS) 8252593: [TESTBUG] serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java failed with JVMTI_ERROR_INVALID_SLOT

2020-09-02 Thread Reingruber, Richard
Hi, please help review this fix for a TESTBUG in serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java Webrev: http://cr.openjdk.java.net/~rrich/webrevs/8252593/webrev.0/ Bug:https://bugs.openjdk.java.net/browse/JDK-8252593 With this change the JVMTI test agent silently acce

Re: RFR(L) 8227745: Enable Escape Analysis for Better Performance in the Presence of JVMTI Agents

2020-09-02 Thread Robbin Ehn
Hi Richard, On 2020-09-02 15:48, Reingruber, Richard wrote: Hi Robbin, // taking the discussion back to the mailing lists > I still don't understand why you don't deoptimize the objects inside the > handshake/safepoint instead? So for handshakes using asynch handshake and allowing bloc

Re: RFR(XS) 8252593: [TESTBUG] serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java failed with JVMTI_ERROR_INVALID_SLOT

2020-09-02 Thread serguei.spit...@oracle.com
Hi Richard, This looks reasonable to me. The only question is about the quality of this testing. How are we sure these errors are caused by races but not bugs in the GetLocalObject implementation? Thanks, Serguei On 9/

RE: RFR(L) 8227745: Enable Escape Analysis for Better Performance in the Presence of JVMTI Agents

2020-09-02 Thread Reingruber, Richard
Hi Robin, > On 2020-09-02 15:48, Reingruber, Richard wrote: > > Hi Robbin, > > > > // taking the discussion back to the mailing lists > > > >> I still don't understand why you don't deoptimize the objects inside > > the > >> handshake/safepoint instead? > So for handshakes using asynch

Re: RFR(XS) 8252593: [TESTBUG] serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java failed with JVMTI_ERROR_INVALID_SLOT

2020-09-02 Thread David Holmes
Hi Richard, On 3/09/2020 12:37 am, Reingruber, Richard wrote: Hi, please help review this fix for  a TESTBUG in serviceability/jvmti/GetLocalVariable/GetLocalWithoutSuspendTest.java Webrev: http://cr.openjdk.java.net/~rrich/webrevs/8252593/webrev.0/ Bug:    https://bugs.openjdk.java.net/browse