On Tue, 28 Oct 2025 08:51:10 GMT, Erik Österlund <[email protected]> wrote:
>> src/hotspot/share/cds/aotThread.hpp line 33:
>>
>>> 31: // A hidden from external view JavaThread for materializing archived
>>> objects
>>> 32:
>>> 33: class AOTThread : public JavaThread {
>>
>> Short names are good but this one don't provide any information about what
>> it does.
>> How about `AOTHeapLoadingThread`?
>
> I was sort of thinking that there might be more AOT cache work that could
> benefit from concurrency, other than object loading. That's why I named it a
> bit more generically. Does that make sense? Otherwise, I'm open to renaming
> it.
There is an other AOT thread `TrainingReplayThread` (also JavaThread) which has
loop to process AOT dependencies for classes which were initialized.
And we have 2 AOT compiler threads (for C1 and C2) to load AOT code.
As you see we have specialized threads for AOT work.
May be I can use this AOTthread for AOT code preloading
(AOTCodeCache::preload_code()) which is currently done in main thread.
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/27732#discussion_r2470435493
