[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Thu, 14 Jan 2016 17:30:55 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: dynamic linker command line invocation
On Tue, Jan 12, 2016 at 05:24:02PM +0100, Markus Wichmann wrote:
> On Mon, Jan 11, 2016 at 12:03:37PM -0500, N Jain wrote:
> > Hi Marcus,
> >
> > Thanks. I am able to get this part working.
> > I am facing one more issue during dynamic linking and need some help to
> > understand how to resolve it.
> >
> > In below code part of __dls3 function I found that TPIDRURO register is
> > being used to read the threadId.
> > I would like to understand how kernel should set this value ?
> >
>
> It shouldn't. musl calls __set_thread_area() (in __init_tp()), and that
> has to set this register.
Yes. The syscall made by __set_thread_area (it's an ARM-private
syscall on ARM, for no good reason, rather than actually being
SYS_set_thread_area) is supposed to set TPIDRURO for the calling
thread to the address provided by the caller.
Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
