From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M0dTk-0007Pt-AT for qemu-devel@nongnu.org; Sun, 03 May 2009 11:19:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M0dTf-0007Lo-Jy for qemu-devel@nongnu.org; Sun, 03 May 2009 11:19:43 -0400 Received: from [199.232.76.173] (port=33359 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M0dTf-0007Lj-BP for qemu-devel@nongnu.org; Sun, 03 May 2009 11:19:39 -0400 Received: from mx2.redhat.com ([66.187.237.31]:57243) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M0dTd-00081S-VO for qemu-devel@nongnu.org; Sun, 03 May 2009 11:19:39 -0400 Message-ID: <49FDB603.6010603@redhat.com> Date: Sun, 03 May 2009 18:19:31 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Import KVM headers including Makefile andimport script References: <1241298173-20668-1-git-send-email-aliguori@us.ibm.com> <49FD341C.8030205@redhat.com> <49FDB2FF.3060001@us.ibm.com> In-Reply-To: <49FDB2FF.3060001@us.ibm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, Hollis Blanchard Anthony Liguori wrote: >> Can we put them under kvm/, as include/ looks like a generic include >> directory, which this isn't. Also, this generates a gratuitous >> conflict with qemu-kvm.git, and we have enough of those already. > > I'd rather put them under linux/ because right now, we depend on a > number of Linux headers (for USB pass through, for instance). > > The qemu-kvm.git layout is kvm/kernel/include. That doesn't seem to > make a lot of sense for QEMU. linux/ makes sense. But let's coordinate the change. > >> I also suggest using arch/*/include/asm as a way of avoiding the >> symlink, instead of the extra hack in fixup.sed. >> > > I did it the current way to avoid deep directory layouts. We would > end up with an extra level of directories via linux/arch-x86/asm/foo.h > as opposed to linux/asm-x86/foo.h. > > Did you have a reason for wanting to avoid the sed hacks verses a > layout like this other than to avoid the hack? Hacks are not good. I'd avoid them whenever possible. Just as an example, we'll need to hack the hack whenever we add an architecture (ia64, s390, arm...). I don't see a problem with the extra directory level, especially as tab completion expands it immediately. > > The fixup certainly can be made more readable. For instance: > > # Expand asm/ includes to avoid having to do symlink trickery > s:^#include $:\ > #if defined(__x86_64__) || defined(__i386__) \ > #include \ > #elif defined(__powerpc__) \ > #include \ > #endif\ > :g > Let's avoid it altogether (we can avoid the compiler.h hack by adding a dummy ). -- error compiling committee.c: too many arguments to function