Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v4]

2022-04-07 Thread Thomas Stuefe
On Mon, 4 Apr 2022 17:51:28 GMT, Roman Kennke wrote: >> JVMTI heap walking marks objects in order to track which have been visited >> already. In order to do that, it uses bits in the object header. Those are >> the same bits that are also used by some GCs to mark objects (the lowest two >> bi

Re: RFR: 8284495: [testbug] Adapt nsk tests to the RISC-V platform

2022-04-07 Thread Leonid Mesnik
On Thu, 7 Apr 2022 05:47:56 GMT, Feilong Jiang wrote: > Add riscv which doesn't have shared memory connector. > Following tests passed with this patch and > [CODETOOLS-7903138](https://github.com/openjdk/jtreg/pull/66): > > - vmTestbase/nsk/jdb/options/connect/connect003/connect003.java > - vmT

Integrated: 8284444: Sting typo

2022-04-07 Thread Daniel Jeliński
On Wed, 6 Apr 2022 12:07:30 GMT, Daniel Jeliński wrote: > This patch adds missing `r` in `string`s This pull request has now been integrated. Changeset: 5bafcfdc Author:Daniel Jeliński URL: https://git.openjdk.java.net/jdk/commit/5bafcfdc171b5a514ecf620703e77fa2f4a49c58 Stats: 1

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v4]

2022-04-07 Thread Roman Kennke
On Thu, 7 Apr 2022 13:31:31 GMT, Thomas Stuefe wrote: > Since the JVMTI heap walk usually walks the whole heap, the bitmap may not be > as sparse as we think. It would materialize a lot - possibly all - of its > fragments. The increased memory consumption during JVMTI heap walk may mess > with

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v4]

2022-04-07 Thread Thomas Stuefe
On Mon, 4 Apr 2022 17:51:28 GMT, Roman Kennke wrote: >> JVMTI heap walking marks objects in order to track which have been visited >> already. In order to do that, it uses bits in the object header. Those are >> the same bits that are also used by some GCs to mark objects (the lowest two >> bi

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v5]

2022-04-07 Thread Roman Kennke
> JVMTI heap walking marks objects in order to track which have been visited > already. In order to do that, it uses bits in the object header. Those are > the same bits that are also used by some GCs to mark objects (the lowest two > bits, also used by locking code). Some GCs also use the bits

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v4]

2022-04-07 Thread Roman Kennke
On Thu, 7 Apr 2022 16:37:22 GMT, Thomas Stuefe wrote: > If you add my proposed comment for bitset.hpp, or some variation of it, then > the rest looks good to me in its current form. Thanks for considering my > proposals! > > Thanks, Thomas I did that, and some more of your suggestions, please

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v5]

2022-04-07 Thread Thomas Stuefe
On Thu, 7 Apr 2022 17:20:41 GMT, Roman Kennke wrote: >> JVMTI heap walking marks objects in order to track which have been visited >> already. In order to do that, it uses bits in the object header. Those are >> the same bits that are also used by some GCs to mark objects (the lowest two >> bi

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v5]

2022-04-07 Thread Thomas Stuefe
On Thu, 7 Apr 2022 17:22:12 GMT, Thomas Stuefe wrote: >> Roman Kennke has updated the pull request incrementally with four additional >> commits since the last revision: >> >> - Add comment describing ObjectBitSet >> - Refactor JVMTI usage of ObjectBitSet >> - Typedef ObjectBitSet to JFRBitS

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v5]

2022-04-07 Thread Thomas Stuefe
On Thu, 7 Apr 2022 17:20:41 GMT, Roman Kennke wrote: >> JVMTI heap walking marks objects in order to track which have been visited >> already. In order to do that, it uses bits in the object header. Those are >> the same bits that are also used by some GCs to mark objects (the lowest two >> bi

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v5]

2022-04-07 Thread Roman Kennke
On Thu, 7 Apr 2022 17:20:41 GMT, Roman Kennke wrote: >> JVMTI heap walking marks objects in order to track which have been visited >> already. In order to do that, it uses bits in the object header. Those are >> the same bits that are also used by some GCs to mark objects (the lowest two >> bi

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v6]

2022-04-07 Thread Roman Kennke
> JVMTI heap walking marks objects in order to track which have been visited > already. In order to do that, it uses bits in the object header. Those are > the same bits that are also used by some GCs to mark objects (the lowest two > bits, also used by locking code). Some GCs also use the bits

Integrated: 8284043: com/sun/jdi/MethodInvokeWithTraceOnTest.java failing with com.sun.jdi.ObjectCollectedException

2022-04-07 Thread Chris Plummer
On Thu, 31 Mar 2022 04:09:55 GMT, Chris Plummer wrote: > Test is getting an `com.sun.jdi.ObjectCollectedException` during an invoke. > The reason is because an allocated object is not being prevented from being > gc'd: > > > StringReference stringObj = vm().mirrorOf("test string"); >

Re: RFR: 8284495: [testbug] Adapt nsk tests to the RISC-V platform

2022-04-07 Thread Chris Plummer
On Thu, 7 Apr 2022 05:47:56 GMT, Feilong Jiang wrote: > Add riscv which doesn't have shared memory connector. > Following tests passed with this patch and > [CODETOOLS-7903138](https://github.com/openjdk/jtreg/pull/66): > > - vmTestbase/nsk/jdb/options/connect/connect003/connect003.java > - vmT

Re: RFR: 8284458: CodeHeapState::aggregate() leaks blob_name [v3]

2022-04-07 Thread Zhengyu Gu
On Thu, 7 Apr 2022 10:12:21 GMT, Lutz Schmidt wrote: >> Zhengyu Gu has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Fix > > Looks good to me. > Good catch! Thanks for finding and fixing the leak. Thanks for the review, @RealLucy ---

Re: RFR: 8284458: CodeHeapState::aggregate() leaks blob_name [v3]

2022-04-07 Thread Leonid Mesnik
On Thu, 7 Apr 2022 02:57:29 GMT, Zhengyu Gu wrote: >> Please review this small patch to fix a possible memory leak. >> >> Test: >> - [x] hotspot_serviceability > > Zhengyu Gu has updated the pull request incrementally with one additional > commit since the last revision: > > Fix Marked as r

Integrated: 8284458: CodeHeapState::aggregate() leaks blob_name

2022-04-07 Thread Zhengyu Gu
On Wed, 6 Apr 2022 23:30:13 GMT, Zhengyu Gu wrote: > Please review this small patch to fix a possible memory leak. > > Test: > - [x] hotspot_serviceability This pull request has now been integrated. Changeset: d4a48843 Author:Zhengyu Gu URL: https://git.openjdk.java.net/jdk/commit/

Re: RFR: 8284458: CodeHeapState::aggregate() leaks blob_name [v3]

2022-04-07 Thread Zhengyu Gu
On Thu, 7 Apr 2022 20:09:24 GMT, Leonid Mesnik wrote: >> Zhengyu Gu has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Fix > > Marked as reviewed by lmesnik (Reviewer). Thanks, @lmesnik - PR: https://git.openjdk.java.net/jdk/

RFR: 8284556: Ensure reachability of classes in runtime/whitebox/TestHiddenClassIsAlive.java and serviceability/dcmd/vm/ClassLoaderHierarchyTest.java

2022-04-07 Thread Leonid Mesnik
Tests are updated to ensure that classes are alive while test checks them. Actually, fixed by @AlanBateman in repo-loom. - Commit messages: - 8284556: Ensure reachability of classes in runtime/whitebox/TestHiddenClassIsAlive.java and serviceability/dcmd/vm/ClassLoaderHierarchyTest.

Re: RFR: 8284556: Ensure reachability of classes in runtime/whitebox/TestHiddenClassIsAlive.java and serviceability/dcmd/vm/ClassLoaderHierarchyTest.java

2022-04-07 Thread Chris Plummer
On Thu, 7 Apr 2022 23:29:41 GMT, Leonid Mesnik wrote: > Tests are updated to ensure that classes are alive while test checks them. > Actually, fixed by @AlanBateman in repo-loom. Marked as reviewed by cjplummer (Reviewer). - PR: https://git.openjdk.java.net/jdk/pull/8152

Re: RFR: 8284495: [testbug] Adapt nsk tests to the RISC-V platform

2022-04-07 Thread Feilong Jiang
On Thu, 7 Apr 2022 14:49:41 GMT, Leonid Mesnik wrote: >> Add riscv which doesn't have shared memory connector. >> Following tests passed with this patch and >> [CODETOOLS-7903138](https://github.com/openjdk/jtreg/pull/66): >> >> - vmTestbase/nsk/jdb/options/connect/connect003/connect003.java >>

Integrated: 8284495: [testbug] Adapt nsk tests to the RISC-V platform

2022-04-07 Thread Feilong Jiang
On Thu, 7 Apr 2022 05:47:56 GMT, Feilong Jiang wrote: > Add riscv which doesn't have shared memory connector. > Following tests passed with this patch and > [CODETOOLS-7903138](https://github.com/openjdk/jtreg/pull/66): > > - vmTestbase/nsk/jdb/options/connect/connect003/connect003.java > - vmT

Re: RFR: 8283710: JVMTI: Use BitSet for object marking

2022-04-07 Thread Kim Barrett
On Mon, 4 Apr 2022 21:53:28 GMT, Roman Kennke wrote: > > One open question is which MEMFLAGS to use. mtTracing doesn't seem to be > > exactly right. Should I templatize BitSet and make JVMTI use > > mtServiceability and JRF use mtTracing as it did before? > > Yes, I think templatizing for MEMF

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v6]

2022-04-07 Thread Kim Barrett
On Thu, 7 Apr 2022 18:28:42 GMT, Roman Kennke wrote: >> JVMTI heap walking marks objects in order to track which have been visited >> already. In order to do that, it uses bits in the object header. Those are >> the same bits that are also used by some GCs to mark objects (the lowest two >> bi

Re: RFR: 8283710: JVMTI: Use BitSet for object marking

2022-04-07 Thread Thomas Stuefe
On Fri, 8 Apr 2022 02:01:50 GMT, Kim Barrett wrote: > > > One open question is which MEMFLAGS to use. mtTracing doesn't seem to be > > > exactly right. Should I templatize BitSet and make JVMTI use > > > mtServiceability and JRF use mtTracing as it did before? > > > > > > Yes, I think templat

Re: RFR: 8284330: jcmd may not be able to find processes in the container [v2]

2022-04-07 Thread Ioi Lam
On Wed, 6 Apr 2022 12:44:35 GMT, Yasumasa Suenaga wrote: >> jcmd uses >> src/jdk.internal.jvmstat/linux/classes/sun/jvmstat/PlatformSupportImpl.java >> to scan temporary directories to find out processes in the container. It >> checks inode to ensure the temp directory is not conflicted. Howev

Re: RFR: 8283710: JVMTI: Use BitSet for object marking [v6]

2022-04-07 Thread Thomas Stuefe
On Thu, 7 Apr 2022 18:28:42 GMT, Roman Kennke wrote: >> JVMTI heap walking marks objects in order to track which have been visited >> already. In order to do that, it uses bits in the object header. Those are >> the same bits that are also used by some GCs to mark objects (the lowest two >> bi

Re: RFR: 8284330: jcmd may not be able to find processes in the container [v2]

2022-04-07 Thread Thomas Stuefe
On Wed, 6 Apr 2022 12:44:35 GMT, Yasumasa Suenaga wrote: >> jcmd uses >> src/jdk.internal.jvmstat/linux/classes/sun/jvmstat/PlatformSupportImpl.java >> to scan temporary directories to find out processes in the container. It >> checks inode to ensure the temp directory is not conflicted. Howev