From: "Rafael Ávila de Espíndola" <rafael.espindola@ic.unicamp.br>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] still trying to use TLS
Date: Mon, 13 Sep 2004 18:09:05 -0300 [thread overview]
Message-ID: <200409131809.05221.rafael.espindola@ic.unicamp.br> (raw)
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
I have successfully fixed the problem of the code generated by one thread
being invalid for another. The solution is to generate code with the gs
prefix and compute the offsets from gs:0.
One think that is missing is to simulate the per thread gdt that the kernel
maintains (ie. alter the simulated gdt when clone is called with
CLONE_SETTLS). I will study how qemu simulates the segments and see if I can
implement that.
Rafael
[-- Attachment #2: qemu.patch.gz --]
[-- Type: application/x-gzip, Size: 3460 bytes --]
reply other threads:[~2004-09-13 21:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200409131809.05221.rafael.espindola@ic.unicamp.br \
--to=rafael.espindola@ic.unicamp.br \
--cc=qemu-devel@nongnu.org \
/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).