[Qemu-devel] Re: Qemu-devel Digest, Vol 86, Issue 533

[Suporte <suporte@indexdata.com.br>]

QtEmu 1.0.5 in Linux KDuXPv1.97 , workfine.....

qemu-devel-request@nongnu.org escreveu:
> Send Qemu-devel mailing list submissions to
> 	qemu-devel@nongnu.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.nongnu.org/mailman/listinfo/qemu-devel
> or, via email, send a message with subject or body 'help' to
> 	qemu-devel-request@nongnu.org
>
> You can reach the person managing the list at
> 	qemu-devel-owner@nongnu.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Qemu-devel digest..."
>
>
> Today's Topics:
>
>    1. [PATCH 2/3] qemu-thread: add cleanup_push() and	cleanup_pop()
>       (Corentin Chary)
>    2. (no subject)
>    3. [PATCH 0/3] [RFC] Threaded vnc server (Corentin Chary)
>    4. [PATCH 1/3] qemu-thread: add qemu_mutex/cond_destroy	and
>       qemu_mutex_exit (Corentin Chary)
>    5. Re: [PATCH] savevm: Really verify if a drive supports
>       snapshots (Markus Armbruster)
>    6. Re: [PATCH] Name the default PCI bus "pci.0" on all
>       architectures (Markus Armbruster)
>    7. (no subject)
>    8. Re: cg14 (Bob Breuer)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 29 May 2010 09:38:05 +0200
> From: Corentin Chary <corentincj@iksaif.net>
> Subject: [Qemu-devel] [PATCH 2/3] qemu-thread: add cleanup_push() and
> 	cleanup_pop()
> To: qemu-devel@nongnu.org
> Cc: Corentin Chary <corentincj@iksaif.net>,	Anthony Liguori
> 	<aliguori@linux.vnet.ibm.com>,	Gautham R Shenoy <ego@in.ibm.com>,
> 	Alexander Graf <agraf@suse.de>, Adam Litke <agl@us.ibm.com>
> Message-ID: <1275118686-15649-3-git-send-email-corentincj@iksaif.net>
>
>
>
> ------------------------------
>
> Message: 2
> Message-ID: <mailman.100.1275148431.11256.qemu-devel@nongnu.org>
>
>  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.
>
> These two functions are implemented using macros because there is no
> other way to do that (pthread man, again):
>
>  On Linux, the pthread_cleanup_push() and pthread_cleanup_pop()
>  functions are implemented as macros that expand to text  containing
>  '{'  and  '}',  respectively.  This means that variables declared
>  within the scope of paired calls to these functions will only
>  be visible within that scope.
>
> Signed-off-by: Corentin Chary <corentincj@iksaif.net>
> ---
>  qemu-thread.h |    4 ++++
>  1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/qemu-thread.h b/qemu-thread.h
> index 19bb30c..e5006bb 100644
> --- a/qemu-thread.h
> +++ b/qemu-thread.h
> @@ -41,4 +41,8 @@ void qemu_thread_self(QemuThread *thread);
>  int qemu_thread_equal(QemuThread *thread1, QemuThread *thread2);
>  void qemu_thread_exit(void *retval);
>  
> +#define qemu_thread_cleanup_pop(execute) pthread_cleanup_pop(execute)
> +#define qemu_thread_cleanup_push(routine, arg)  \
> +    pthread_cleanup_push(routine, arg)
> +
>  #endif
>