From: Paolo Bonzini <pbonzini@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Qemu-development List <qemu-devel@nongnu.org>,
Anthony Liguori <aliguori@linux.vnet.ibm.com>,
Alexander Graf <agraf@suse.de>,
Corentin Chary <corentin.chary@gmail.com>,
Gautham R Shenoy <ego@in.ibm.com>
Subject: [Qemu-devel] Re: [PATCH v2 2/2] vnc: threaded VNC server
Date: Mon, 07 Jun 2010 15:36:37 +0200 [thread overview]
Message-ID: <4C0CF5E5.8040800@redhat.com> (raw)
In-Reply-To: <4C0BA885.5060909@redhat.com>
On 06/06/2010 03:54 PM, Avi Kivity wrote:
> One option is to disable vnc on Windows and let a Windows maintainer
> materialize and add the corresponding support.
Adding Windows support to qemu-threads must be done anyway sooner or
later and most of the code can be found for example in git.
Being a QEMU/Windows maintainer is a bit harder than that though,
especially if at some point someone would like iothread to become the
only supported option...
Paolo
next prev parent reply other threads:[~2010-06-07 13:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 13:20 [Qemu-devel] [PATCH v2 0/2] Threaded VNC server Corentin Chary
2010-06-04 13:20 ` [Qemu-devel] [PATCH v2 1/2] qemu-thread: add qemu_mutex/cond_destroy and qemu_mutex_exit Corentin Chary
2010-06-04 13:20 ` [Qemu-devel] [PATCH v2 2/2] vnc: threaded VNC server Corentin Chary
2010-06-04 13:25 ` [Qemu-devel] " Alexander Graf
2010-06-04 13:53 ` Corentin Chary
2010-06-04 13:44 ` Alexander Graf
2010-06-05 8:03 ` Corentin Chary
2010-06-06 13:54 ` Avi Kivity
2010-06-06 14:39 ` Corentin Chary
2010-06-07 13:36 ` Paolo Bonzini [this message]
2010-06-04 14:41 ` Paolo Bonzini
2010-06-04 14:55 ` Corentin Chary
2010-06-04 15:11 ` Paolo Bonzini
2010-06-06 14:11 ` [Qemu-devel] " Avi Kivity
2010-06-06 14:48 ` Corentin Chary
2010-06-06 14:53 ` Avi Kivity
2010-06-06 15:16 ` 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=4C0CF5E5.8040800@redhat.com \
--to=pbonzini@redhat.com \
--cc=agraf@suse.de \
--cc=aliguori@linux.vnet.ibm.com \
--cc=avi@redhat.com \
--cc=corentin.chary@gmail.com \
--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 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).