From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] [WIP]Added target to build libvdisk
Date: Mon, 31 Oct 2011 11:01:13 +0100 [thread overview]
Message-ID: <j8lrl8$mvn$1@dough.gmane.org> (raw)
In-Reply-To: <4EAD91B1.40109@redhat.com>
On 10/30/2011 07:04 PM, Saggi Mizrahi wrote:
>>
>> I wonder also what thread API should be used, qemu_thread versions
>> used internally or standard ones. It would be logical to use
>> qemu_thread versions but then the external user should use those too.
> I would prefer not to use qemu's threading as it'll expose internal
> APIs. I suggest glib's threading,
Is it visible in any way to the client? Also, perhaps thread-safety
should be left to the client so that they can use whatever API they like?
Paolo
next prev parent reply other threads:[~2011-10-31 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 16:51 [Qemu-devel] [PATCH 1/2] Better support for distros using /lib64 directories Saggi Mizrahi
2011-10-30 16:51 ` [Qemu-devel] [PATCH 2/2] [WIP]Added target to build libvdisk Saggi Mizrahi
2011-10-30 17:21 ` Blue Swirl
2011-10-30 18:04 ` Saggi Mizrahi
2011-10-31 10:01 ` Paolo Bonzini [this message]
2011-10-31 10:04 ` [Qemu-devel] [PATCH 1/2] Better support for distros using /lib64 directories Paolo Bonzini
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='j8lrl8$mvn$1@dough.gmane.org' \
--to=pbonzini@redhat.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.