From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MMJBT-0004O2-GT for qemu-devel@nongnu.org; Thu, 02 Jul 2009 06:06:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MMJBO-0004NS-G2 for qemu-devel@nongnu.org; Thu, 02 Jul 2009 06:06:27 -0400 Received: from [199.232.76.173] (port=39791 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MMJBO-0004NP-1M for qemu-devel@nongnu.org; Thu, 02 Jul 2009 06:06:22 -0400 Received: from va3ehsobe001.messaging.microsoft.com ([216.32.180.11]:43891 helo=VA3EHSOBE001.bigfish.com) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_ARCFOUR_MD5:16) (Exim 4.60) (envelope-from ) id 1MMJBN-0004FA-MW for qemu-devel@nongnu.org; Thu, 02 Jul 2009 06:06:21 -0400 Message-ID: <4A4C8686.4020908@amd.com> Date: Thu, 2 Jul 2009 12:05:58 +0200 From: Andre Przywara MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] target-i386/kvm.c vs. qemu-kvm-x86.c List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, kvm@vger.kernel.org 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? Thanks and regards, Andre. -- Andre Przywara AMD-OSRC (Dresden) Tel: x29712