From mboxrd@z Thu Jan 1 00:00:00 1970 From: Catalin Marinas Subject: Re: [PATCH RFC 1/6] [HACK!] arm64/xen: create links to arch/arm include files and Xen code Date: Fri, 31 May 2013 11:36:17 +0100 Message-ID: <20130531103617.GA18045@localhost.cambridge.arm.com> References: <1369930713-6063-1-git-send-email-stefano.stabellini@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <1369930713-6063-1-git-send-email-stefano.stabellini@eu.citrix.com> Sender: linux-kernel-owner@vger.kernel.org To: Stefano Stabellini Cc: "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "xen-devel@lists.xensource.com" , Will Deacon , "Ian.Campbell@citrix.com" , "konrad.wilk@oracle.com" List-Id: xen-devel@lists.xenproject.org On Thu, May 30, 2013 at 05:18:28PM +0100, Stefano Stabellini wrote: > Most of Xen support for ARM is common between ARMv7 and ARMv8. > Create links to the code under arch/arm (bleah). > > Other, probably better alternatives: > > - move the code to a different location, maybe the header files to > include/xen/arm and the code to drivers/xen/arm (still pretty ugly)? > > - create a copy of the code to arch/arm64 (even worse); KVM handles this in the Makefile by referencing back to arch/arm or even the generic kvm directory. I think that's the 'cleanest' ;) -- Catalin