From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752884AbbBMOiG (ORCPT ); Fri, 13 Feb 2015 09:38:06 -0500 Received: from lhrrgout.huawei.com ([194.213.3.17]:50552 "EHLO lhrrgout.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752378AbbBMOiE (ORCPT ); Fri, 13 Feb 2015 09:38:04 -0500 X-Greylist: delayed 400 seconds by postgrey-1.27 at vger.kernel.org; Fri, 13 Feb 2015 09:38:03 EST Message-ID: <54DE0A9C.7080505@huawei.com> Date: Fri, 13 Feb 2015 15:30:52 +0100 From: Claudio Fontana User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: Andre Przywara , Pekka Enberg , Sasha Levin , Cyrill Gorcunov , Asias He CC: "kvm@vger.kernel.org" , Marc Zyngier , Will Deacon , "linux-kernel@vger.kernel.org" , Ronald Minnich , "kvmarm@lists.cs.columbia.edu" , "linux-arm-kernel@lists.infradead.org" Subject: Re: stand-alone kvmtool References: <54DDD465.3050300@arm.com> In-Reply-To: <54DDD465.3050300@arm.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Originating-IP: [10.203.60.76] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Andre, On 13.02.2015 11:39, Andre Przywara wrote: > Hi, > > as I found it increasingly inconvenient to use kvmtool[1] as part of a > Linux repository, I decided to give it a go and make it a stand-alone > project. So I filtered all the respective commits, adjusted the paths in > there (while keeping authorship and commit date, of course) and then > added the missing bits to let it compile without a kernel tree nearby. > The result is now available on: > > git://linux-arm.org/kvmtool.git > http://linux-arm.org/kvmtool.git It builds fine on x86_64, but when I tried to crosscompile from x86_64 to AArch64, I get in trouble because of libfdt: I have the aarch64 libs (static and shared), but how do I instruct the build system to get it from the right place? Thanks, Claudio > > You can simply check it out, type make and use "./lkvm run" for a quick > test. So far I briefly tested x86-64, arm and arm64, the later two were > also cross-compiled. For sure there are rough edges in there (for > instance copying a few non-uapi header files into), but I deem it worthy > enough to get some public comments. > For me that also fixed some nasty warnings about libfdt, which now are > gone due it using your system library version of it. > I also managed to get rid of the libc-i386-dev dependency when compiling > for x86-64, but that still needs to be cleaned up and thus is not in the > current HEAD. > I haven't got around to compile-test the other supported architectures, > but supporting them should be as easy as copying over the uapi kvm.h > header file (see the respective ARM commit). Contributions (and tests!) > are welcome. > > Please give it a go and tell me what you think. I don't want to fork the > project, so I am happy if someone "official" picks it up. > > Cheers, > Andre. > > [1] https://github.com/penberg/linux-kvm/tree/master/tools/kvm > _______________________________________________ > kvmarm mailing list > kvmarm@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/kvmarm > -- Claudio Fontana Server Virtualization Architect Huawei Technologies Duesseldorf GmbH Riesstraße 25 - 80992 München office: +49 89 158834 4135 mobile: +49 15253060158