From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andre Przywara <andre.przywara@amd.com>
Subject: target-i386/kvm.c vs. qemu-kvm-x86.c
Date: Thu, 2 Jul 2009 12:05:58 +0200
Message-ID: <4A4C8686.4020908@amd.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Return-path: <kvm-owner@vger.kernel.org>
Received: from va3ehsobe001.messaging.microsoft.com ([216.32.180.11]:43890
	"EHLO VA3EHSOBE001.bigfish.com" rhost-flags-OK-OK-OK-FAIL)
	by vger.kernel.org with ESMTP id S1752580AbZGBKGQ (ORCPT
	<rfc822;kvm@vger.kernel.org>); Thu, 2 Jul 2009 06:06:16 -0400
Sender: kvm-owner@vger.kernel.org
List-ID: <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