From: Christoph Hellwig <hch@infradead.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Chris Wright <chrisw@redhat.com>,
kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: KVM call minutes for Feb 1
Date: Tue, 1 Feb 2011 12:53:36 -0500 [thread overview]
Message-ID: <20110201175336.GA22653@infradead.org> (raw)
In-Reply-To: <4D48367D.2060802@siemens.com>
On Tue, Feb 01, 2011 at 05:36:13PM +0100, Jan Kiszka wrote:
> kvm_cpu_exec/kvm_run, and start wondering "What needs to be done to
> upstream so that qemu-kvm could use that implementation?". If they
> differ, the reasons need to be understood and patched away, either by
> fixing/enhancing upstream or simplifying qemu-kvm. Once the upstream
> changes are merged back, a qemu-kvm patch is posted to switch to that
> version.
while I'm not an expert in that area I really like you're approach. I'd
really prefer to let you finish up all the major work that way before
starting massive revamping like the glib main loop. Resolving the
qemu/qemu-kvm schisma surely is more important for the overall project
than rewriting existing functionality to look a little nicer.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: KVM call minutes for Feb 1
Date: Tue, 1 Feb 2011 12:53:36 -0500 [thread overview]
Message-ID: <20110201175336.GA22653@infradead.org> (raw)
In-Reply-To: <4D48367D.2060802@siemens.com>
On Tue, Feb 01, 2011 at 05:36:13PM +0100, Jan Kiszka wrote:
> kvm_cpu_exec/kvm_run, and start wondering "What needs to be done to
> upstream so that qemu-kvm could use that implementation?". If they
> differ, the reasons need to be understood and patched away, either by
> fixing/enhancing upstream or simplifying qemu-kvm. Once the upstream
> changes are merged back, a qemu-kvm patch is posted to switch to that
> version.
while I'm not an expert in that area I really like you're approach. I'd
really prefer to let you finish up all the major work that way before
starting massive revamping like the glib main loop. Resolving the
qemu/qemu-kvm schisma surely is more important for the overall project
than rewriting existing functionality to look a little nicer.
next prev parent reply other threads:[~2011-02-01 17:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 15:54 KVM call minutes for Feb 1 Chris Wright
2011-02-01 15:54 ` [Qemu-devel] " Chris Wright
2011-02-01 16:36 ` Jan Kiszka
2011-02-01 16:36 ` [Qemu-devel] " Jan Kiszka
2011-02-01 16:53 ` Anthony Liguori
2011-02-01 16:53 ` [Qemu-devel] " Anthony Liguori
2011-02-01 17:03 ` Jan Kiszka
2011-02-01 17:03 ` [Qemu-devel] " Jan Kiszka
2011-02-01 17:20 ` Anthony Liguori
2011-02-01 17:20 ` [Qemu-devel] " Anthony Liguori
2011-02-01 17:34 ` Jan Kiszka
2011-02-01 17:34 ` [Qemu-devel] " Jan Kiszka
2011-02-01 20:28 ` Anthony Liguori
2011-02-03 10:11 ` Marcelo Tosatti
2011-02-03 10:11 ` [Qemu-devel] " Marcelo Tosatti
2011-02-03 13:48 ` Anthony Liguori
2011-02-03 13:48 ` Anthony Liguori
2011-02-01 17:53 ` Christoph Hellwig [this message]
2011-02-01 17:53 ` Christoph Hellwig
2011-02-03 10:13 ` Marcelo Tosatti
2011-02-03 10:13 ` [Qemu-devel] " Marcelo Tosatti
2011-02-03 12:36 ` Paolo Bonzini
2011-02-03 12:36 ` [Qemu-devel] " Paolo Bonzini
2011-02-03 14:54 ` Anthony Liguori
2011-02-03 14:54 ` [Qemu-devel] " 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=20110201175336.GA22653@infradead.org \
--to=hch@infradead.org \
--cc=chrisw@redhat.com \
--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 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.