From: Fabrice Bellard <fabrice@bellard.org>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org, thayne@c2.net
Subject: Re: [Qemu-devel] [PATCH] arm eabi TLS
Date: Thu, 13 Dec 2007 09:57:11 +0100 [thread overview]
Message-ID: <4760F3E7.9000208@bellard.org> (raw)
In-Reply-To: <200712130121.04204.paul@codesourcery.com>
Paul Brook wrote:
>> - It would be good to limit the changes in the CPU emulation code to
>> handle the TLS. For example, on MIPS, the TLS register must not be
>> stored in the CPU state. Same for ARM.
>
> I disagree. The TLS register is part of the CPU state. On many machines
> (including ARMv6 CPUs) it's an actual CPU register. I'm fairly sure the same
> is true for recent MIPS revisions.
If some CPUs implement it in hardware, then I agree.
Fabrice.
next prev parent reply other threads:[~2007-12-13 8:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 0:44 [Qemu-devel] [PATCH] arm eabi TLS Thayne Harbaugh
2007-12-12 1:29 ` Paul Brook
2007-12-12 23:03 ` Fabrice Bellard
2007-12-13 1:21 ` Paul Brook
2007-12-13 1:15 ` Thayne Harbaugh
2008-01-28 18:27 ` Felipe Contreras
2008-04-04 15:03 ` Marc-André Lureau
2008-04-04 17:48 ` Stuart Anderson
2008-05-05 15:12 ` Felipe Contreras
2007-12-13 8:57 ` Fabrice Bellard [this message]
2007-12-13 13:28 ` Daniel Jacobowitz
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=4760F3E7.9000208@bellard.org \
--to=fabrice@bellard.org \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=thayne@c2.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).