Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Jul 2013 00:34:58 +0300
From:      Konstantin Belousov <>
To:        Davide Italiano <>
Subject:   Re: Accessing struct pthread from kernel
Message-ID:  <>
In-Reply-To: <>
References:  <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Jul 06, 2013 at 01:22:05AM +0200, Davide Italiano wrote:
> Hi,
> as a preliminary step in the implementation of adaptive spinning for
> umtx, I'm switching the pthread/umtx code so that a thread that
> acquires a pthread_mutex writes the address of struct pthread in the
> owner field of the lock instead of the thread id (tid). This is
> because having struct pthread pointer allows easily to access
> informations of the thread, and makes easy to get the state of the
> thread exported from the kernel (once this will be implemented).
> For what concerns the libthr side, the internal function
> _get_curthread() goes into the TLS to obtain the struct field of
> curthread, so I'm done.
> OTOH, I'm quite unsure instead about how to get address of struct
> pthread for curthread from the kernel side (for example, in
> do_lock_umutex() sys/kern/kern_umtx.c).
You should not, see below.

> I guess I need to write some MD code because the TLS is different on
> the various architecture supported in FreeBSD, and as a first step I
> focused on amd64.
> It looks like from the SDM that %%fs register points to the base of
> the TLS, so I think that accessing using curthread->td_pcb->pcb_fsbase
> (and then adding the proper offset to acces the right field) is a
> viable solution to do this. Am I correct?
> In particular what worries me is if the read of 'struct pthread' for
> curthread from the TLS register is atomic with respect to preemptions.
> Alternatively, is there an (easier way) to accomplish this task?

Coupling the libthr thread structure and kernel makes the ABI cast in
stone and avoids most possibilities of changing the libthr internals.
The same is true for kernel accessing the userspace TLS area of the thread.

If you want kernel<->usermode communication of the thread run state,
and possibly also a way to advisory prevent a preemption of the
spinning usermode thread, you should create a dedicated parameter block
communicated from usermode to kernel on thread creation. For the main
thread, the block could be allocated by kernel by image activator,
placed on the stack and its address passed to the usermode by auxv.

Note that you cannot access the usermode from the context switch
code. Wiring the corresponding page is very wasteful (think about a
process with 10,000 threads) and still does not provide any guarantees
since usermode can unmap or remap the range. You might see my 'fast
sigprocmask' patches where somewhat similar idea was implemented.

I also recommend you to look at the Solaris schedctl(2).

Content-Type: application/pgp-signature

Version: GnuPG v2.0.20 (FreeBSD)



Want to link to this message? Use this URL: <>