RFR: 8225035: Thread stack size issue caused by large TLS size
Jiangli Zhou
jianglizhou at google.com
Sat Jun 15 17:58:19 UTC 2019
Hi Thomas,
I came across this doc:
https://android.googlesource.com/platform/bionic/+/master/docs/elf-tls.md.
It has a good amount of general description about static TLS block (on
stack) and dynamic TLS block, in addition to the information provided by
Florian and Andrew in the thread.
Best regards,
Jiangli
On Wed, Jun 12, 2019 at 12:34 PM Thomas Stüfe <thomas.stuefe at gmail.com>
wrote:
> On Wed, Jun 12, 2019 at 6:51 PM Andrew Haley <aph at redhat.com> wrote:
>
> > On 6/12/19 5:05 PM, Thomas Stüfe wrote:
> >
> > > I am currently trying to find out the answer to my original
> > > question: what - in this figure
> > > (
> >
> https://docs.oracle.com/cd/E19253-01/817-1984/6mhm7plaa/index.html#chapter8-fig-1
> > > - I assume that is the correct one for x64?) - is located on the
> > > thread stack, and where.
> >
> > The stuff on the left-hand side of that diagram is on the thread stack,
> > the rest is
> > dynamically allocated elsewhere.
> >
> >
> Does that mean that TLS from libjvm.so or JNI libraries does not live on
> thread stacks, since those libraries are dynamically loaded and therefore
> would be allocated elsewhere (right side of the picture)?
>
>
> > --
> > Andrew Haley
> > Java Platform Lead Engineer
> > Red Hat UK Ltd. <https://www.redhat.com>
> > https://keybase.io/andrewhaley
> > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671
> >
>
More information about the hotspot-runtime-dev
mailing list