From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Corentin Chary <corentincj@iksaif.net>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Adam Litke <agl@us.ibm.com>, Alexander Graf <agraf@suse.de>,
Gautham R Shenoy <ego@in.ibm.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] qemu-thread: add cleanup_push() and cleanup_pop()
Date: Thu, 3 Jun 2010 06:50:38 +0100 [thread overview]
Message-ID: <201006030650.38903.paul@codesourcery.com> (raw)
In-Reply-To: <1275118686-15649-3-git-send-email-corentincj@iksaif.net>
> From pthread man:
>
> These functions manipulate the calling thread's stack of
> thread-cancellation clean-up handlers. A clean-up handler is
> a function that is automatically executed when a thread is canceled
> [...] it might, for example, unlock a mutex so that it becomes
> available to other threads in the process.
Do we really need to use thread cancellation?
It's one of those features that makes me extremely nervous. Especially in C
code where people generally aren't expecting exceptions to be thrown.
Paul
next prev parent reply other threads:[~2010-06-03 5:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 7:38 [Qemu-devel] [PATCH 0/3] [RFC] Threaded vnc server Corentin Chary
2010-05-29 7:38 ` [Qemu-devel] [PATCH 1/3] qemu-thread: add qemu_mutex/cond_destroy and qemu_mutex_exit Corentin Chary
2010-05-29 7:38 ` [Qemu-devel] [PATCH 2/3] qemu-thread: add cleanup_push() and cleanup_pop() Corentin Chary
2010-06-03 5:50 ` Paul Brook [this message]
2010-06-03 7:27 ` [Qemu-devel] " Paolo Bonzini
2010-06-03 7:46 ` Corentin Chary
2010-05-29 7:38 ` [Qemu-devel] [PATCH 3/3] vnc: threaded VNC server Corentin Chary
2010-06-03 7:55 ` [Qemu-devel] " Paolo Bonzini
2010-06-03 8:26 ` Corentin Chary
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=201006030650.38903.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=agl@us.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@linux.vnet.ibm.com \
--cc=corentincj@iksaif.net \
--cc=ego@in.ibm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.