From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org, kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: [Qemu-devel] Merging KVM QEMU changes upstream
Date: Fri, 25 Jan 2008 11:53:50 -0600 [thread overview]
Message-ID: <479A222E.4@us.ibm.com> (raw)
Hi,
As most probably know, the KVM project has been maintaining a QEMU tree
for some time now. Beyond support for the KVM kernel interface, the
tree also contains a number of useful features like live migration,
virtio, and extboot. Some of these things have been posted to
qemu-devel already but were not included.
I would like to work on merging the KVM changes into upstream QEMU but
before I started that work, I wanted to get a read on how difficult it
would be. A lot of these things were designed specifically for KVM on
x86. Only now are other architectures starting to be considered.
Certainly, cross-architecture emulation hasn't really been considered.
I wouldn't expect anything to be merged that caused a regression for
cross-architecture emulation, but I don't really have the time to get a
lot of the new features working for the cross-architecture case. I
would expect, though, that if these things were merged, it would make it
relatively easy for someone else to do that though.
Is this a reasonable merge strategy? We won't introduce regressions but
I can't guarantee these new things will work cross-architecture.
Regards,
Anthony Liguori
next reply other threads:[~2008-01-25 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 17:53 Anthony Liguori [this message]
2008-01-25 18:43 ` [Qemu-devel] Merging KVM QEMU changes upstream Paul Brook
2008-01-25 18:50 ` [kvm-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=479A222E.4@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--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).