qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Chris Wright <chrisw@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for Feb 1
Date: Thu, 03 Feb 2011 13:36:20 +0100	[thread overview]
Message-ID: <4D4AA144.3070005@redhat.com> (raw)
In-Reply-To: <20110201175336.GA22653@infradead.org>

On 02/01/2011 06:53 PM, Christoph Hellwig wrote:
> I'd really prefer to let you finish up all the major work that way
> before starting massive revamping like the glib main loop.

Yes, the glib main loop is not going to go anywhere if it cannot be 
applied to both qemu and qemu-kvm.

(And, I believe a new main loop is a necessary condition to show that 
glib is bringing benefits.  It's basically impossible to interface with 
external libraries as long as we have our own main loop).

Paolo

  parent reply	other threads:[~2011-02-03 12:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 15:54 [Qemu-devel] KVM call minutes for Feb 1 Chris Wright
2011-02-01 16:36 ` [Qemu-devel] " Jan Kiszka
2011-02-01 16:53   ` Anthony Liguori
2011-02-01 17:03     ` Jan Kiszka
2011-02-01 17:20       ` Anthony Liguori
2011-02-01 17:34         ` Jan Kiszka
2011-02-01 20:28           ` Anthony Liguori
2011-02-03 10:11           ` Marcelo Tosatti
2011-02-03 13:48             ` Anthony Liguori
2011-02-01 17:53   ` Christoph Hellwig
2011-02-03 10:13     ` Marcelo Tosatti
2011-02-03 12:36     ` Paolo Bonzini [this message]
2011-02-03 14:54       ` Anthony Liguori

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=4D4AA144.3070005@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=hch@infradead.org \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.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).