Date: Mon, 22 Jan 2007 23:11:57 +0100 From: Divacky Roman <xdivac02@stud.fit.vutbr.cz> To: Tijl Coosemans <tijl@ulyssis.org> Cc: freebsd-emulation@freebsd.org, jkim@freebsd.org Subject: Re: linuxolator: tls_test results amd64 Message-ID: <20070122221157.GA54796@stud.fit.vutbr.cz> In-Reply-To: <20070122212624.GA49466@stud.fit.vutbr.cz> References: <790a9fff0701211041j1176d00gd6dd75d0989cf4ec@mail.gmail.com> <200701220001.22404.tijl@ulyssis.org> <20070122081810.GA42976@stud.fit.vutbr.cz> <200701221752.21628.tijl@ulyssis.org> <20070122212624.GA49466@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
> overall you are saying that to support linux32 tls we have to > > 1) load an unused segment with proper values > 2) return the number of the segment from the set_thread_syscall > 3) make the automatic loading/unloading of that segment to happen on > every context switch (just like its done for segment 3 on i386) rethought it a little and I think I understand now... I think simple reloading the segment thats used for TLS (which one is it?) on fbsd@amd64 should do the trick. what do you think? so instead of rewriting just the base address we reload the whole segment. that should not be that hard. but I dont understand the connection between fs/gs and the segment. is it that reloading fs_base resets the base in the segment the fs points at? roman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070122221157.GA54796>