From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH 03/15] xen: Add a new target to qemu: target-xen Date: Fri, 13 Aug 2010 13:50:35 -0500 Message-ID: <4C6593FB.2050008@codemonkey.ws> References: <1281622202-3453-3-git-send-email-stefano.stabellini@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1281622202-3453-3-git-send-email-stefano.stabellini@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: stefano.stabellini@eu.citrix.com Cc: Anthony.Perard@citrix.com, xen-devel@lists.xensource.com, qemu-devel@nongnu.org List-Id: xen-devel@lists.xenproject.org On 08/12/2010 09:09 AM, stefano.stabellini@eu.citrix.com wrote: > From: Anthony PERARD > > This patch adds a new Xen device model target to Qemu, called > target-xen. > A xen specific target is definitely the wrong approach. I understand the desire to avoid the TCG code. We would like to (optionally) do the same in KVM. The right way to do this though is to make it possible to build without TCG by wrapping the common interfaces in a function pointer table. > diff --git a/target-xen/exec-dm.c b/target-xen/exec-dm.c > new file mode 100644 > index 0000000..3d64695 > --- /dev/null > +++ b/target-xen/exec-dm.c > This takes a non-target specific file and makes it target specific. This is not a reasonable approach. What's the issue with the existing exec.c? Regards, Anthony Liguori