From owner-freebsd-arch@FreeBSD.ORG Fri Feb 10 17:36:48 2012 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F15C21065670 for ; Fri, 10 Feb 2012 17:36:48 +0000 (UTC) (envelope-from gonzo@hq.bluezbox.com) Received: from hq.bluezbox.com (hq.bluezbox.com [70.38.37.145]) by mx1.freebsd.org (Postfix) with ESMTP id ACE168FC0A for ; Fri, 10 Feb 2012 17:36:48 +0000 (UTC) Received: from [24.87.53.93] (helo=[192.168.1.116]) by hq.bluezbox.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1RvuOj-000MDI-2H; Fri, 10 Feb 2012 09:36:40 -0800 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Oleksandr Tymoshenko In-Reply-To: <20120210105726.GO1860@hoeg.nl> Date: Fri, 10 Feb 2012 09:36:40 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <94EAEADD-440A-4148-B9CC-B7BED1BCF206@bluezbox.com> References: <58175263-109E-4FF0-BB29-E0331C01DCD5@FreeBSD.org> <20120208215122.GA28769@alchemy.franken.de> <20120210105726.GO1860@hoeg.nl> To: Ed Schouten X-Mailer: Apple Mail (2.1084) Sender: gonzo@hq.bluezbox.com X-Spam-Level: --- X-Spam-Report: Spam detection software, running on the system "hq.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 2012-02-10, at 2:57 AM, Ed Schouten wrote: > Hi Marius, > > * Marius Strobl , 20120208 22:51: >> See lib/libc/stdlib/malloc.c, arm and mips currently are the only >> supported FreeBSD architectures that have no support for TLS. > > Just out of curiosity, what is needed to make TLS work? Is it just the > lack of support by our toolchain or is there also stuff on our side that > needs to be done? [...] Content analysis details: (-3.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] 0.6 AWL AWL: From: address is in the auto white-list Cc: freebsd-arch@freebsd.org, David Chisnall , Marius Strobl Subject: Re: NO_TLS flag for public headers X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Feb 2012 17:36:49 -0000 On 2012-02-10, at 2:57 AM, Ed Schouten wrote: > Hi Marius, >=20 > * Marius Strobl , 20120208 22:51: >> See lib/libc/stdlib/malloc.c, arm and mips currently are the only >> supported FreeBSD architectures that have no support for TLS. >=20 > Just out of curiosity, what is needed to make TLS work? Is it just the > lack of support by our toolchain or is there also stuff on our side = that > needs to be done? There are several places that should be fixed and in sync in order to = get TLS=20 working for architecture: rtld-elf, libthr, cpu_set_user_tls in kernel = and thread pointer handling in toolchain. Look at my commits as of Feb 9 - = they cover all of these but toolchain part. TLS on MIPS is fixed for the simplest test case. TLS data in dynamic = library=20 might need some more work for rtld, but not much. I'll take a look at = ARM when I have=20 working root over NFS on my ARM board. That is if nobody step up and fix = it soon :)=20=