From patchwork Wed Oct 21 14:20:42 2009 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: wolfgang.mauerer@siemens.com X-Patchwork-Id: 55080 Received: from vger.kernel.org (vger.kernel.org [209.132.176.167]) by demeter.kernel.org (8.14.2/8.14.2) with ESMTP id n9LEIgFh010066 for ; Wed, 21 Oct 2009 14:18:42 GMT Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753550AbZJUOSP (ORCPT ); Wed, 21 Oct 2009 10:18:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753551AbZJUOSN (ORCPT ); Wed, 21 Oct 2009 10:18:13 -0400 Received: from lizzard.sbs.de ([194.138.37.39]:22343 "EHLO lizzard.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753547AbZJUOSK (ORCPT ); Wed, 21 Oct 2009 10:18:10 -0400 Received: from mail1.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id n9LEIAJB010289; Wed, 21 Oct 2009 16:18:10 +0200 Received: from [139.25.109.82] (mchn315c.mchp.siemens.de [139.25.109.82]) by mail1.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id n9LEIAHj022918; Wed, 21 Oct 2009 16:18:10 +0200 Message-ID: <4ADF18BA.9090807@siemens.com> Date: Wed, 21 Oct 2009 16:20:42 +0200 From: Wolfgang Mauerer User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Dietmar Maurer CC: "kvm@vger.kernel.org" , "Kiszka, Jan" Subject: Re: [PATCH 2/2] kvm-kmod: Document the build process References: <1256040699-27468-1-git-send-email-wolfgang.mauerer@siemens.com> <1256040699-27468-2-git-send-email-wolfgang.mauerer@siemens.com> <90D306BE6EBC8D428A824FBBA7A3113D0127975B06@ronja.maurer-it.com> In-Reply-To: <90D306BE6EBC8D428A824FBBA7A3113D0127975B06@ronja.maurer-it.com> Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org diff --git a/README b/README index 40a72d3..34cc51a 100644 --- a/README +++ b/README @@ -1,16 +1,21 @@ Building the KVM kernel module is performed differently depending on whether you are working from a clone of the git repository or from a source release. +Notice that two kernels are involved: One from which the KVM sources +are taken (kernel A), and one for which the module is built (kernel B). +For out-of-tree module builds, it is well possible that kernel A is more +recent than kernel B. - To build from a release, simply use ./configure (possibly with any arguments that are required for your setup, see ./configure --help) - and make. + and make. The kernel specified with --kerneldir refers to kernel B, + that is, the kernel for which the module is built. - Building from a cloned git repository requires a kernel tree with the main - kvm sources that is included as a submodule in the linux-2.6/ directory. By - default, the KVM development tree on git.kernel.org is used, but you can - change this setting in .gitmodules + kvm sources (kernel A) that is included as a submodule in the linux-2.6/ + directory. By default, the KVM development tree on git.kernel.org is used, + but you can change this setting in .gitmodules - Before the kvm module can be built, the linux submodule must be initialised + Before the kvm module can be built, the linux submodule must be initialised and populated. The required sequence of commands is git submodule init @@ -24,3 +29,5 @@ you are working from a clone of the git repository or from a source release. make sync LINUX=/path/to/tree + The synchronisation stage refers to kernel A, that is, the kernel + from which the KVM sources are taken.