qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Lauro Ramos Venancio <lauro.venancio@openbossa.org>
Subject: Re: [Qemu-devel] [PATCH] implement CLONE_CHILD_CLEARTID
Date: Thu, 16 Oct 2008 14:19:38 +0100	[thread overview]
Message-ID: <200810161419.39245.paul@codesourcery.com> (raw)
In-Reply-To: <1224111451.7266.39.camel@laurov-desktop>

On Wednesday 15 October 2008, Lauro Ramos Venancio wrote:
> The attached patch implements the clone flag CLONE_CHILD_CLEARTID.

Using the host set_tid_address is wrong. This is liable to break the host 
libc/libpthread.  The current set_tid_address implementation is similarly 
broken.

Paul

  reply	other threads:[~2008-10-16 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 22:57 [Qemu-devel] [PATCH] implement CLONE_CHILD_CLEARTID Lauro Ramos Venancio
2008-10-16 13:19 ` Paul Brook [this message]
2008-10-16 14:28   ` Lauro Ramos Venancio
  -- strict thread matches above, loose matches on Subject: below --
2009-02-02  9:19 Riku Voipio
2008-10-15 22:18 Lauro Ramos Venancio

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=200810161419.39245.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=lauro.venancio@openbossa.org \
    --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).