From: Avi Kivity <avi@redhat.com>
To: Andre Przywara <andre.przywara@amd.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: target-i386/kvm.c vs. qemu-kvm-x86.c
Date: Thu, 02 Jul 2009 13:13:24 +0300 [thread overview]
Message-ID: <4A4C8844.4070209@redhat.com> (raw)
In-Reply-To: <4A4C8686.4020908@amd.com>
On 07/02/2009 01:05 PM, Andre Przywara wrote:
> Hi,
>
> the lastest qemu -> qemu-kvm sync pulled the kvm_trim_features()
> function from QEMU's target-i386/kvm.c into the qemu-kvm tree, where
> it is already defined in qemu-kvm-x86.c (which does not exist in
> qemu.git).
> AFAICS qemu-kvm only uses the last file, so the target-i386 code is
> not triggered.
> What is the future of these two files? Will one vanish? Will they be
> merged? Where to put new features in?
All of the above.
The goal is to merge the features of qemu-kvm.c and qemu-kvm-x86.c into
kvm-all.c and kvm.c, eventually removing the former. In general new
features need to be added in both.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-07-02 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 10:05 [Qemu-devel] target-i386/kvm.c vs. qemu-kvm-x86.c Andre Przywara
2009-07-02 10:13 ` Avi Kivity [this message]
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=4A4C8844.4070209@redhat.com \
--to=avi@redhat.com \
--cc=andre.przywara@amd.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).