qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thayne Harbaugh <thayne@c2.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] What happened with NPTL/TLS support?
Date: Fri, 12 Oct 2007 12:22:58 -0600	[thread overview]
Message-ID: <1192213378.5280.13.camel@phantasm.home.enterpriseandprosperity.com> (raw)
In-Reply-To: <94a0d4530710120812r397d626dvb3044b08e30ebdce@mail.gmail.com>


On Fri, 2007-10-12 at 18:12 +0300, Felipe Contreras wrote:
> Hi,
> 
> When I try to use codesourcery's toolchain arm-2006q3-27 in my Fedora
> 7 box I always have the following issue:
> 
> qemu: Unsupported syscall: 983045

Yep, I've seen that before.

> I guess it's a problem of NPTL incompatibility. Anyway, the patch that
> Paul Brook sent a while ago solves it [1].
> 
> I wonder if it can be integrated or what would be the right way to
> solve this issue. Am I the only one having it?
> 
> Best regards.
> 
> [1] http://lists.gnu.org/archive/html/qemu-devel/2005-08/msg00128.html


I've been using this patch, as well as other NPTL/TLS patches as well as
some of my own work and have a set of patches for NPTL/TLS that works
reasonably well for arm and i386.  The patches don't apply cleanly to
CVS current, but I'm more than happy to rework them so that they will if
someone is serious about getting NPTL/TLS/futex stuff working for
linux-user.  I haven't submitted my patches because I kept expecting the
other patches to be accepted.

  reply	other threads:[~2007-10-12 18:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-12 15:12 [Qemu-devel] What happened with NPTL/TLS support? Felipe Contreras
2007-10-12 18:22 ` Thayne Harbaugh [this message]
2007-10-20 20:34   ` Thiemo Seufer
2007-10-22 14:26     ` Thayne Harbaugh
2007-11-02 13:28       ` Felipe Contreras
2007-11-02 17:06         ` Thayne Harbaugh
2007-10-15  1:06 ` Paul Brook

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=1192213378.5280.13.camel@phantasm.home.enterpriseandprosperity.com \
    --to=thayne@c2.net \
    --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).