From: cinap_lenrek@gmx.de
To: 9fans@9fans.net
Subject: Re: [9fans] why not Lvx for Plan 9?
Date: Thu, 10 Jul 2008 21:25:13 +0200 [thread overview]
Message-ID: <c1e8ba590a5a3e67c79a8009133004fe@gmx.de> (raw)
In-Reply-To: <13426df10807100936l14a08d45n714428b086897d65@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
Ok, here is the thing...
Here are 2 versions of linux libc tls and notls. (Current linux distries just
ship with the tls version i think, but here may be exceptions)
TLS is a libpthread thing that is heavily wired together with libc
on linux. (just do an ldd on something like ls)
TLS uses the two free segment registers %FS and %GS as a way for a thread
to access its thread local storage area. (the parent allocates some memory
and sets up an segment descriptor that points/translates to this memory
(it makes set_thread_area() syscall todo this)
to implement this syscall, i needed a way to change entries in the
global descriptor table in the kernel. here is some experimental
driver (/dev/tls) but i'm not sure if its correct. also it buys you not very mutch
to have it yet, because the new pthread library also needs a futex implementation
to be usefull. the old notls libc works without that syscall and doesnt need
any modification to the plan9 kernel.
but... i think in the near future TLS support is important and for that i
need some kernel support to change segment descriptors on a process
basis.
If i understand vx correctly, it also needs a way to change segment
descriptors and even needs to be able to change its %DS, %CS, %SS registers
to it.
cinap
[-- Attachment #2: Type: message/rfc822, Size: 2815 bytes --]
From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] why not Lvx for Plan 9?
Date: Thu, 10 Jul 2008 09:36:22 -0700
Message-ID: <13426df10807100936l14a08d45n714428b086897d65@mail.gmail.com>
On Thu, Jul 10, 2008 at 9:33 AM, Charles Forsyth <forsyth@terzarima.net> wrote:
>> speaking of which, did Cinap's fixes for the gs segment make it in so
>> we have thread local storage a la linux now?
>
>
> or did you mean in linuxemu?
yes. linuxemu needed a kernel change IIRC and I was wondering if that was in.
ron
next prev parent reply other threads:[~2008-07-10 19:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-08 15:28 kokamoto
2008-07-08 15:58 ` David Leimbach
2008-07-08 16:04 ` erik quanstrom
2008-07-08 16:33 ` ron minnich
2008-07-08 16:47 ` Charles Forsyth
2008-07-09 4:33 ` LiteStar numnums
2008-07-08 17:46 ` Eric Van Hensbergen
2008-07-08 17:49 ` erik quanstrom
2008-07-08 18:38 ` a
2008-07-08 19:01 ` erik quanstrom
2008-07-08 19:46 ` a
2008-07-08 20:03 ` Eric Van Hensbergen
2008-07-08 20:15 ` William Josephson
2008-07-08 20:38 ` Eric Van Hensbergen
2008-07-08 21:25 ` ron minnich
2008-07-08 22:16 ` Steve Simon
2008-07-08 22:32 ` David du Colombier
2008-07-09 0:01 ` don bailey
2008-07-09 0:13 ` ron minnich
2008-07-09 3:17 ` Eric Van Hensbergen
2008-07-09 3:43 ` ron minnich
2008-07-09 3:45 ` erik quanstrom
2008-07-09 4:44 ` David Leimbach
2008-07-08 18:50 ` David Leimbach
2008-07-08 17:19 ` Skip Tavakkolian
2008-07-10 12:58 ` matt
2008-07-10 13:47 ` Russ Cox
2008-07-10 14:03 ` erik quanstrom
[not found] ` <B94154D0-97B5-4FFF-A140-E47D95FC1307@flyingwalrus.net>
2008-07-12 15:59 ` erik quanstrom
2008-07-10 15:18 ` ron minnich
2008-07-10 16:33 ` Charles Forsyth
2008-07-10 16:36 ` ron minnich
2008-07-10 19:25 ` cinap_lenrek [this message]
2008-07-10 19:50 ` ron minnich
2008-07-11 9:10 ` Kernel Panic
2008-07-11 16:12 ` ron minnich
2008-07-10 14:01 ` erik quanstrom
2008-07-08 17:27 ` Russ Cox
2008-07-08 17:39 ` a
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c1e8ba590a5a3e67c79a8009133004fe@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).