public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Wolfgang Mauerer <wolfgang.mauerer@siemens.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] kvm-kmod: Document the build process (take 2)
Date: Sat, 14 Nov 2009 10:08:37 +0100	[thread overview]
Message-ID: <4AFE7395.1090307@web.de> (raw)
In-Reply-To: <1258047322-5750-1-git-send-email-wolfgang.mauerer@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 2261 bytes --]

Wolfgang Mauerer wrote:
> A package without build instructions is like a kernel
> without a penguin.

Thanks, merged.

Jan

> 
> Signed-off-by: Wolfgang Mauerer <wolfgang.mauerer@siemens.com>
> ---
>  README |   37 +++++++++++++++++++++++++++++++++++++
>  1 files changed, 37 insertions(+), 0 deletions(-)
>  create mode 100644 README
> 
> diff --git a/README b/README
> new file mode 100644
> index 0000000..bef7586
> --- /dev/null
> +++ b/README
> @@ -0,0 +1,37 @@
> +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 (this is the default case), simply
> +  use ./configure (possibly with any arguments that are required for
> +  your setup, see ./configure --help) 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 (most likely useful for developers
> +  only) requires a kernel tree with the main 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 this can be
> +  changed in the git configuration.
> +
> +  Before the kvm module can be built, the linux submodule must be initialised
> +  and populated. The required sequence of commands is
> +
> +  git submodule init
> +  git submodule update
> +  ./configure
> +  make sync
> +  make
> +
> +  Notice that you can also specify an existing Linux tree for the
> +  synchronisation stage by using
> +
> +  make sync LINUX=/path/to/kernel/A
> +
> +  LINUX specifies the path to kernel A from which the KVM sources are taken. 
> +  The directory must point to a local git tree, not to a plain directory
> +  containing the kernel sources. If LINUX is unset, the default value
> +  is linux-2.6/, i.e., the git submodule.



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  reply	other threads:[~2009-11-14  9:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 12:11 [PATCH 1/2] kvm-kmod: Use the main development tree of kvm as Linux submodule wolfgang.mauerer
2009-10-20 12:11 ` [PATCH 2/2] kvm-kmod: Document the build process wolfgang.mauerer
2009-10-21 10:43   ` Dietmar Maurer
2009-10-21 14:20     ` Wolfgang Mauerer
2009-10-22 20:54       ` Dietmar Maurer
2009-10-23  7:50         ` Jan Kiszka
2009-11-12 17:35           ` [PATCH] kvm-kmod: Document the build process (take 2) Wolfgang Mauerer
2009-11-14  9:08             ` Jan Kiszka [this message]
2009-10-22 15:15 ` [PATCH 1/2] kvm-kmod: Use the main development tree of kvm as Linux submodule Avi Kivity
2009-10-22 16:13   ` Wolfgang Mauerer
2009-10-22 16:17     ` Avi Kivity
2009-10-22 16:25       ` Wolfgang Mauerer
2009-10-22 16:35         ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AFE7395.1090307@web.de \
    --to=jan.kiszka@web.de \
    --cc=kvm@vger.kernel.org \
    --cc=wolfgang.mauerer@siemens.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox